Re: Xcode 3.2 -- Two more bugs??
Re: Xcode 3.2 -- Two more bugs??
- Subject: Re: Xcode 3.2 -- Two more bugs??
- From: Jim Ingham <email@hidden>
- Date: Mon, 31 Aug 2009 10:08:37 -0700
The reason for doing this was to make "Auto-attach Debugger on Crash"
more reliable. If you turn off "Auto-attach Debugger on Crash" in the
Debugging pane of the Executable Editor for the project you're
running, then your app won't be run under the debugger.
There are some cases where it is necessary not to run under the
debugger - particularly if you want to "run" apps that use some kind
of protection scheme to prevent debugging of your app. In these
cases, the Auto Attach wasn't going to work anyway, so there's no
problem with turning it off.
But if there are other reasons why you don't want to run your app
under the debugger in the normal "Run" mode it would be interesting to
hear what they are. We tested the way Xcode runs apps under the
debugger in 3.2 with a wide variety of apps, and having the debugger
involved only added a fraction of a second, so that should not be a
big deal. If there are other problems, please file a bug and we'll
take a look.
JIm
On Aug 31, 2009, at 8:49 AM, Joar Wingfors wrote:
1. Whenever I choose "Run" (any variant), GDB starts up! To date,
I have
not been able to "Run" anything without this happening. Is this a
bug or a
feature? I have seen one other posting with the same complaint
but no
response.
Feature. When you launch from Xcode 3.2, you're always going through
GDB. Historically, the primary reason for using Run over Debug has
been that it's much faster to Run - This is still the case in Xcode
3.2.
_______________________________________________
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