This is the mail archive of the gcc-bugs@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: SEGV in libstdc++-v3 caused when fn attached is called the second time...


The program that triggers this bug consists of about 15 source files...
Should I attach them all? (In a new bug report, of course)  And, I forgot my
Bugzilla passwd.  D'oh!
----- Original Message ----- 
From: "Jim Wilson" <wilson@specifixinc.com>
To: "The Thodes" <aspiesrule@mcleodusa.net>
Cc: <gcc-bugs@gcc.gnu.org>
Sent: Tuesday, June 08, 2004 2:54 AM
Subject: Re: SEGV in libstdc++-v3 caused when fn attached is called the
second time...


> The Thodes wrote:
> > The attached .ii file, when compiled and linked with support code that
calls
> > it twice with valid args both times, causes a SEGV in libstdc++-v3's
_M_grab
> > implementation...
>
> Bugs should be reported into our bugzilla database rather than sent to
> gcc-bugs.  We do not track bugs reported by email, so you are more
> likely to get a useful answer if you file it into bugzilla.  See
>      http://gcc.gnu.org/bugs.html
> for more info on reporting bugs.
>
> This does not seem to be a complete testcase.  I get a linker error for
> an undefined main function when I compile it.  If we can't reproduce the
> problem you reported, then we won't be able to look at it.
>
> It isn't clear if there is any useful info in the gdb output you
> included.  You haven't annotated any of it, so it is hard to tell what
> it is for.  Was there something specific you were trying to demonstrate
> in the gdb output?
> -- 
> Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com
>
>
>



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