This is the mail archive of the
mailing list for the GCC project.
Re: libstdc++/6784: SEGV using istream >> operator under gcc-3.1/sun-sparc-solaris2.6
Phil Edwards wrote:
> On Fri, May 24, 2002 at 09:27:42AM -0700, Benjamin Kosnik wrote:
>>>#0 0xff30c620 in number () from /usr/lib/libc.so.1
>>>#1 0xff30c290 in __doscan_u () from /usr/lib/libc.so.1
>>>#2 0xff310e90 in sscanf () from /usr/lib/libc.so.1
>>Ooooh yeah. I remember this. This is a bug in libc's sscanf and extreme
>>input. You'll have to talk to Sun.
Thanks for this information.
Although, I probably shouldn't have mentioned it in this bug report,
since it isn't anything to do with the problem that I am seeing :-)
This fails on both Solaris2.6 and Solaris2.8.
Whereas, the failures
FAIL: 21_strings/inserters_extractors.cc execution test
FAIL: 24_iterators/istream_iterator.cc execution test
FAIL: 26_numerics/complex_inserters_extractors.cc execution test
FAIL: 27_io/instantiations.cc execution test
FAIL: 27_io/istream_extractor_char.cc execution test
FAIL: 27_io/istream_extractor_other.cc execution test
FAIL: 27_io/istream_manip.cc execution test
FAIL: 27_io/istream_seeks.cc execution test
FAIL: 27_io/istream_sentry.cc execution test
FAIL: 27_io/istream_unformatted.cc execution test
FAIL: 27_io/istringstream_members.cc execution test
FAIL: 27_io/ostream_inserter_arith.cc execution test
FAIL: 27_io/ostream_inserter_other.cc execution test
FAIL: 27_io/stringstream_members.cc execution test
Are specific to Solaris2.6 and all seem to be due to a SEGV in
Andrew Pollard - Senior Software Engineer (APF)
Brooks-PRI Automation - Planning and Logistics Solutions
Email: Andrew.Pollard@brooks-pri.com - Tel: +44 (0)118 9215603