Re: Debugging SenTestingKit UnitTests on Leopard
Re: Debugging SenTestingKit UnitTests on Leopard
- Subject: Re: Debugging SenTestingKit UnitTests on Leopard
- From: Chris Hanson <email@hidden>
- Date: Tue, 13 Nov 2007 13:58:37 -0800
On Nov 13, 2007, at 11:48 AM, Christopher Friesen wrote:
On Nov 12, 2007, at 2:26 PM, Chris Hanson wrote:
What happens is that my app either crashes under the debugger as
soon as I have something more complicated than NSLog(@"got here");
in my test - or that I get the output from the tests running on
the console (and I can see there that my tests do get handled by
OCUnit) but the debugger does not stop on my breakpoints.
Hmm, that should work. One thing that I have run into is that due
to the way gdb launches applications in Xcode 3.0 -- which I think
changed rather late in the game -- you may be injecting your tests
into the shell that is being used to launch your application, or
into one of the commands it runs, which probably won't be too happy.
This is not something new, GDB has always started programs this way
in Xcode.
Doh, thanks for the correction, JI & Chris!
It must be something intermediate between the shell and the running
app that injecting tests into will fail. Something for us to look
into offline. :)
In any case, to reiterate the workaround, add the line
set start-with-shell 0
to your ~/.gdbinit file if you want to debug unit tests that are
injected into an application.
-- Chris
_______________________________________________
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