Re: GDB Crash
Re: GDB Crash
- Subject: Re: GDB Crash
- From: Jim Ingham <email@hidden>
- Date: Thu, 18 Dec 2003 11:07:27 -0800
Have you put a breakpoint on getpid? The Xcode Debugger UI calls
getpid in the your target program once when it starts up (I think it
does this the first time it hits a breakpoint, but the UI folks would
know for sure), and for some reason the call to this function gets
interrupted. The only reason I can think of is that you have a
breakpoint there.
If you do, then you are going to have to disable that breakpoint till
after you have hit your first real breakpoint...
However, I am just guessing. If we can see the Xcode log file, we can
get a better picture of what is going on. To generate this, do:
1) Quit Xcode.
2) In Terminal, say:
$ defaults write com.apple.Xcode PBXGDBDebuggerLogToFile YES
3) Restart Xcode, and do whatever you need to to make it fail.
4) Look in /tmp/<YOUR UID>/TemporaryItems/
There will be a file there called something like:
PBGDB-<Project Name>-<Xcode UID>
which contains the transcript of the gdb/Xcode communications.
Then send this file to me (or even better, file a bug with the
bugreporter.apple.com, and include this information, your description,
and if possible and example project that shows this error...)
Jim
On Dec 18, 2003, at 9:37 AM, Rob Minnis wrote:
I've recently started seeing a somewhat odd error when debugging. Each
time (so far), this error eventually corrects itself but while it is
occurring, it makes debugging virtually impossible. Has anyone else
seen this or have any idea what triggers it?
The program being debugged stopped while in a function called from GDB.
When the function (getpid) is done executing, GDB will silently
stop (instead of continuing to evaluate the expression containing
the function call).
(gdb) continue
Current language: auto; currently asm
/SourceCache/gdb/gdb-292/src/gdb/dummy-frame.c:353: internal-error:
dummy_frame_register_unwind: Assertion `dummy != NULL' failed.
A problem internal to GDB has been detected. Further
debugging may prove unreliable.
The Debugger has exited due to signal 6 (SIGABRT).The Debugger has
exited due to signal 6 (SIGABRT).
When it happens, it occurs when hitting a breakpoint. Adding and
removing breakpoints and rearranging code seems to have no effect.
From the details above, it appears that gdb considers this situation
to
be benign but it is not possible to recover (i.e. pressing continue
causes the abort).
Rob Minnis
email@hidden
_______________________________________________
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.
--
Jim Ingham email@hidden
Developer Tools
Apple Computer
_______________________________________________
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.
References: | |
| >GDB Crash (From: Rob Minnis <email@hidden>) |