Re: Debugger has exited due to signal 11 (SIGSEGV)
Re: Debugger has exited due to signal 11 (SIGSEGV)
- Subject: Re: Debugger has exited due to signal 11 (SIGSEGV)
- From: "Peter CK" <email@hidden>
- Date: Tue, 4 Jul 2006 19:27:08 -0400
> Is gdb killing your code or is gdb itself dying randomly.
It does sound like gdb itself may be dying here. I had similar problems
with Xcode versions prior to 2.3. Are you using the current version?
Try switching between the STABS and DWARF debugging formats.
Not sure if gdb crashed or just chose to kill my app. Either way, it doesn't give me much info on why it happend. I'm still using Xcode
2.2, but I'll have to wait for my company before upgrading. If it makes a difference between v2.2 and v2.3, then it's abviously Xcodes fault. Is the debugging formats specified in the Xcode options somewhere?
As mentioned elsewhere previously on the list you can enable logging for
gdb with:
$ defaults write com.apple.Xcode PBXGDBDebuggerLogToFile YES
$ defaults write com.apple.Xcode PBXGDBDebuggerLogFileName /tmp/gd.log
I'll try that. I was hoping I wouldn't have to get my hands dirty, but at least there is a way to get more info.
Thanks all,
Peter
_______________________________________________
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