public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Andrew Pollard <Andrew.Pollard@brooks-pri.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libstdc++/6784: SEGV using istream >> operator under gcc-3.1/sun-sparc-solaris2.6
Date: Mon, 27 May 2002 04:26:00 -0000 [thread overview]
Message-ID: <20020527112605.27090.qmail@sources.redhat.com> (raw)
The following reply was made to PR libstdc++/6784; it has been noted by GNATS.
From: Andrew Pollard <Andrew.Pollard@brooks-pri.com>
To: Phil Edwards <phil@jaj.com>
Cc: Benjamin Kosnik <bkoz@redhat.com>, bkoz@gcc.gnu.org,
gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Subject: Re: libstdc++/6784: SEGV using istream >> operator under gcc-3.1/sun-sparc-solaris2.6
Date: Mon, 27 May 2002 12:20:15 +0100
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
ctype_inline.h
Andrew
--
Andrew Pollard - Senior Software Engineer (APF)
Brooks-PRI Automation - Planning and Logistics Solutions
Email: Andrew.Pollard@brooks-pri.com - Tel: +44 (0)118 9215603
next reply other threads:[~2002-05-27 11:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-27 4:26 Andrew Pollard [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-29 2:16 bkoz
2002-05-29 2:16 Benjamin Kosnik
2002-05-28 10:18 Andrew Pollard
2002-05-27 4:57 bkoz
2002-05-27 4:53 Benjamin Kosnik
2002-05-27 3:16 Gabriel Dos Reis
2002-05-27 2:46 Benjamin Kosnik
2002-05-27 2:39 Gabriel Dos Reis
2002-05-27 2:36 Benjamin Kosnik
2002-05-26 7:26 Gabriel Dos Reis
2002-05-24 10:27 Phil Edwards
2002-05-24 9:56 Benjamin Kosnik
2002-05-23 10:46 Andrew Pollard
2002-05-23 8:37 bkoz
2002-05-23 6:26 Andrew.Pollard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020527112605.27090.qmail@sources.redhat.com \
--to=andrew.pollard@brooks-pri.com \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).