Re: debug problem [solved]
Re: debug problem [solved]
- Subject: Re: debug problem [solved]
- From: Chris Hanson <email@hidden>
- Date: Sat, 9 Oct 2004 18:40:02 -0700
On Oct 9, 2004, at 5:33 PM, Eric Ocean wrote:
After working with people over on the xcode-users list *(where I moved the discussion after it became clear it was related to a tool issue), it was discovered that the problem was the Test build style I was using for Unit Testing (with SetTestKit). The unit tester would start up my app behind the scenes, which would execute my startup code. Then, the app would restart and I'd drop into the debugger.
Were you by any chance using the "Build and Debug" command instead of the "Debug Executable" command to bring up your application in the debugger?
With Build and Debug, Xcode will do a build and then bring your application up in the debugger if the build is successful. As part of doing the build, it will run the script build phases in the target you're building, which will cause your unit tests to run.
Using a different build style solved the problem.
Another strategy might be to adjust your unit tests so they clean up after they run, so as not to leave state around (in the form of file modifications etc.) that would impact debugging.
-- Chris
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden