Re: debug info after crash using DWARF
Re: debug info after crash using DWARF
- Subject: Re: debug info after crash using DWARF
- From: Jim Ingham <email@hidden>
- Date: Fri, 2 Jun 2006 13:21:14 -0700
The fact that is says "No registers" means that the program has
already exited by the time you are going to look at it. This probably
doesn't have anything to do with DWARF. If you send the complete
debugging session, we can see a little better what's going on. Best
would be to file a bug at bugreporter.apple.com with the Xcode/gdb log
- which you generate by:
1) Quit Xcode.
2) In Terminal, say:
$ defaults write com.apple.Xcode PBXGDBDebuggerLogToFile YES
$ defaults write com.apple.Xcode PBXGDBDebuggerLogFileName /tmp/
IncludeInBug.log
3) Restart Xcode, and do whatever you need to to make it fail.
4) Attach /tmp/IncludeInBug.log to the Radar.
Thanks,
Jim
On Jun 2, 2006, at 12:16 PM, Jan Hegewald wrote:
Hello,
my c++ executable (compiled with g++ and -gdwarf-2) just crashed
during a little debugging session with Xcode/gdb. I noticed I can
not print any variables after the crash in the gdb console. It only
says:
(gdb) p foo
No symbol "foo" in current context.
No registers.
Printing variables this way works very well if I compile with -g
(i.e. stabs format). I just wonder if there is a way to get this
functionality with dwarf too. Maybe I am missing something obvious?
Thanks for any help,
-- Jan
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden