Re: auto-gdb
Re: auto-gdb
- Subject: Re: auto-gdb
- From: Ken Thomases <email@hidden>
- Date: Mon, 8 Mar 2010 10:16:47 -0600
On Mar 8, 2010, at 4:25 AM, Jack Nutting wrote:
> Prior to Xcode 3.2, while running an app from within Xcode (with the
> "Run" command, not just the "Debug" command), any crash in the app
> would magically stop on kill() in gdb, letting me examine things just
> as if I had run it through the debugger in the first place. I know
> this is the way it worked at least in 3.1, but don't know for how long
> it's been that way.
>
> Anyway, that behavior seems to be gone in 3.2, and any app that
> crashes just dumps unceremoniously back to Xcode, with no output in
> the Xcode console log or anything. Is there any way to get the old
> behavior back, besides just always running through gdb?
This is controlled on the Debugging tab of the info window for the Executable: "Auto-attach debugger on crash".
In Xcode 3.2, this actually just does launch it using gdb, always, because the old way had various limitations/quirks that made it less than ideal.
Cheers,
Ken
_______________________________________________
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
| References: | |
| | >auto-gdb (From: Jack Nutting <email@hidden>) |