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: Wed, 5 Jul 2006 08:26:22 -0400
> 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?
If you can get hold of a spare machine I would *highly* recommend trying
out 2.3 on it. We had huge problems with gdb crashing and ignoring
breakpoints in Xcode 2.2. The DWARF debugging format is new to
2.3.
Are you using static libraries? We were, and I think it was the
combination of those and Stabs that caused gdb to baulk. Gdb is now
very stable (well, comparatively at least...)
Hey, thanks for the info. Maybe I can convince my company to upgrade to
2.3.
It would be nice to have a stable debugging experience for a change.
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