--- Comment #8 from drow at gcc dot gnu dot org 2007-08-14 14:08 ---
I don't think there's anything useful we can do with it without a testcase,
unfortunately.
--
drow at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #7 from scovich at gmail dot com 2007-08-13 21:10 ---
(In reply to comment #6)
> Sorry, my mistake. I meant readelf -wi (lowercase I).
>
Unfortunately, I recompiled with 4.1 to get on with debugging, and also updated
to 20070810 later that day. Now the bug won't cooperate
--- Comment #6 from drow at gcc dot gnu dot org 2007-08-13 20:29 ---
Sorry, my mistake. I meant readelf -wi (lowercase I).
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32990
--- Comment #5 from scovich at gmail dot com 2007-08-10 16:50 ---
Murphy strikes again -- 5 minutes after closing this bug it popped back up in
spite of a clean compile. Apparently `make clean' can change which PC causes
complaints but doesn't necessarily fix the problem.
--
scovich
--- Comment #4 from scovich at gmail dot com 2007-08-10 16:39 ---
The problem comes from adding a member function to a header file and only
recompiling some of the source files that include it (make depend missed
something). It looked like a regression because changing versions of gcc
re
--- Comment #3 from scovich at gmail dot com 2007-08-10 16:20 ---
Created an attachment (id=14050)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14050&action=view)
Output of readelf -wf
I'm attaching the output of `readelf -wf' This time around some of offending PC
are 0x41ac8c, 0
--- Comment #2 from drow at gcc dot gnu dot org 2007-08-06 13:21 ---
Subject: Re: New: [Regression] gdb has symbol table issues
On Sat, Aug 04, 2007 at 11:13:11PM -, scovich at gmail dot com wrote:
> When debugging code produced by g++-4.3.0-20070716 the debugger regularly
> outpu
--- Comment #1 from pinskia at gcc dot gnu dot org 2007-08-05 19:50 ---
First if gdb is throwing an internal error, then there is a bug in gdb. Now if
you can prove somehow gcc's debug info is broken, then GCC has a bug. But
until we get a testcase, it is hard to say anything really.
