[uClibc] Problems with vfscanf?
Garrett Kajmowicz
gkajmowi at tbaytel.net
Sat Jan 8 01:23:14 UTC 2005
Are there any known problems with vfscanf in uClibc? More specifically, what
might cause it to segfault?
Backtrace:
#0 0xb776f0e4 in vfscanf () from /lib/libc.so.0
#1 0xb776ef4e in fscanf () from /lib/libc.so.0
#2 0xb77a43de in std::basic_filebuf<char, std::char_traits<char>
>::underflow() () from /usr/lib/libuClibc++.so.0
#3 0xb7b389af in std::basic_streambuf<char, std::char_traits<char> >::sgetc()
(this=0xbfffe32c) at streambuf:96
#4 0xb7b7915f in std::istream::getline(char*, long, char) (this=0xbfffe320,
s=0xbfffbc10 "", n=10000, delim=10 '\n') at istream:175
#5 0xb7b778ed in std::istream::getline(char*, long) (this=0xbfffe320,
s=0xbfffbc10 "", n=10000) at istream:168
#6 0xb7b73e11 in MICOGetOpt::parse(std::string const&, unsigned char)
(this=0xbfffe9e0, _filename=@0xbfffea20, ignore=1 '\001')
at util.cc:606
#7 0xb7b2bd7f in CORBA::ORB_init(int&, char**, char const*)
(argc=@0xbffff1a4, argv=0xbffff1e4, _id=0x81aa318 "") at orb.cc:3241
#8 0x08076a07 in main (argc=1, argv=0xbffff1e4) at main.cc:78
The format string I am passing to fscanf is "%1c"
The address which is being read into is known to be good (I've verified by
printing out pointer addresses), and the file pointer is stdin.
I am using uClibc 0.26-3 as found in uwoody. If I need to upgrade that
version, please let me know if any special process needs to be done.
- Garrett Kajmowicz
More information about the uClibc
mailing list