public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Phil Edwards <phil@jaj.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: Fri, 24 May 2002 10:27:00 -0000 [thread overview] Message-ID: <20020524171605.11554.qmail@sources.redhat.com> (raw) The following reply was made to PR libstdc++/6784; it has been noted by GNATS. From: Phil Edwards <phil@jaj.com> To: Benjamin Kosnik <bkoz@redhat.com> Cc: Andrew Pollard <Andrew.Pollard@brooks-pri.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: Fri, 24 May 2002 13:13:01 -0400 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. I should put this in the system-specific FAQs, then. The nearest bug I could find in Sun's contract database was 4517988, which is SPARC-specific (i.e., x86/Solaris works) and present in Solaris 8. It causes sscanf to segv on long input. I assume that's the bug we're talking about here, although the reported didn't experience it on Sol 8. Phil -- If ye love wealth greater than liberty, the tranquility of servitude greater than the animating contest for freedom, go home and leave us in peace. We seek not your counsel, nor your arms. Crouch down and lick the hand that feeds you; and may posterity forget that ye were our countrymen. - Samuel Adams
next reply other threads:[~2002-05-24 17:16 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-05-24 10:27 Phil Edwards [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-05-29 2:16 Benjamin Kosnik 2002-05-29 2:16 bkoz 2002-05-28 10:18 Andrew Pollard 2002-05-27 4:57 bkoz 2002-05-27 4:53 Benjamin Kosnik 2002-05-27 4:26 Andrew Pollard 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 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=20020524171605.11554.qmail@sources.redhat.com \ --to=phil@jaj.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: linkBe 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).