This is the mail archive of the gcc-prs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: libstdc++/6784: SEGV using istream >> operator under gcc-3.1/sun-sparc-solaris2.6


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]