Exactly. In Xcode 3.1, Xcode would catch the crash and then pass the
exception to gdb, but that was a lossy process. In 3.2, we let gdb
run the program, and that way we can tell exactly what happened when
the program dies. But that means if you have a program that doesn't
run under the debugger, you now need to uncheck the "Auto-attach
debugger on crash" to restore the old behavior.
On Aug 31, 2009, at 12:02 PM, Jens Alfke wrote:
On Aug 31, 2009, at 11:51 AM, Jim Ingham wrote:
No it doesn't mean that. When Xcode is "running" without setting
any breakpoints, there are a lot of the pieces of information gdb
normally gathers that we know it doesn't need. So we cooked up
some startup settings that tell gdb not to notice things like
shared library loading and not to read any symbol information at
all, etc. If you only need to use gdb as a program launcher not a
debugger, it doesn't add much overhead. It's only when you want to
do things like look at symbols or set breakpoints that you start to
pay for having gdb around.
I think I understand now. So is this mode new in 3.2? I just tried
running an app in Xcode 3.1 in the "Breakpoints disabled" mode, and
there is no gdb process running at all.
So far Xcode is by far my top reason for wanting to upgrade to 10.6.
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