gdb debugger weirdness and custom data formatters
gdb debugger weirdness and custom data formatters
- Subject: gdb debugger weirdness and custom data formatters
- From: Mark Lentczner <email@hidden>
- Date: Thu, 5 Feb 2004 13:15:18 -0800
The debugger seems to have lost its mind: In particular, it doesn't
seem to reliably know when some automatic C++ variables are in or out
of scope. When stopped at a breakpoint, I am seeing it sometimes try
to display values for variables that are declared in the current block,
but after the breakpoint. These objects haven't been constructed yet,
and since I'm using a custom data format that calls a method of the
object to obtain a display string, the debugger dies a horrible death
when the method is called on an object that hasn't yet been constructed
(and so is in an inconsistent state).
When the debugger dies, I see:
/SourceCache/gdb/gdb-309/src/gdb/sentinel-frame.c:102: internal-error:
Function sentinal_frame_pop called
A problem internal to GDB has been detected. Further
debugging may prove unreliable.
The Debugger has exited with status 1.The Debugger has exited with
status 1.
Anyone else seen this? This is happening in debugging builds, so there
should be no whacky gcc code motion going on... This all worked like a
charm until very recently.
- Mark
Mark Lentczner
email@hidden
http://www.wheatfarm.org/
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.