This is the mail archive of the
gcc-prs@gcc.gnu.org
mailing list for the GCC project.
Re: libstdc++/6518: ???
- From: bkoz at gcc dot gnu dot org
- To: bkoz at gcc dot gnu dot org, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org, plasmahh at tzi dot de
- Date: 15 May 2002 14:36:58 -0000
- Subject: Re: libstdc++/6518: ???
- Reply-to: bkoz at gcc dot gnu dot org, bkoz at gcc dot gnu dot org, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org, plasmahh at tzi dot de, gcc-gnats at gcc dot gnu dot org
Synopsis: ???
Responsible-Changed-From-To: unassigned->bkoz
Responsible-Changed-By: bkoz
Responsible-Changed-When: Wed May 15 07:36:57 2002
Responsible-Changed-Why:
Mine.
State-Changed-From-To: open->feedback
State-Changed-By: bkoz
State-Changed-When: Wed May 15 07:36:57 2002
State-Changed-Why:
Yikes. I've reproduced this on mainline and the gcc-3.1 branch. What do do with s when NULL is not specified: I've asked the library reflector about this. In the meantime, I've the following patch, which sets failbit and doesn't
crash. Let me know what you think.
http://gcc.gnu.org/ml/gcc-patches/2002-05/msg01205.html
Thanks,
benjamin
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6518