Re: Debugging dependent unit tests under Xcode 3
Re: Debugging dependent unit tests under Xcode 3
- Subject: Re: Debugging dependent unit tests under Xcode 3
- From: Chris Hanson <email@hidden>
- Date: Mon, 10 Mar 2008 16:15:15 -0700
On Mar 10, 2008, at 12:14 PM, Fritz Anderson wrote:
Building the test bundle: As before ("Executed 3 tests"). No
breakpoints hit.
Building + debugging the test bundle: As before. The test runs with
no breakpoints hit, the application launches under the debugger. The
following appears in the Debugger Console:
This is a known issue with debugging unit tests (and anything using
DYLD_INSERT_LIBRARIES in general) in Xcode 3.0. The workaround for it
-- to which the gdb output alludes -- involves adding
set start-with-shell 0
to your ~/.gdbinit file. This prevents gdb from running your
executable within a shell and therefore injecting the test bundle into
the shell.
Separately, the SenTestingKit.framework(Tests) suite is part of OCUnit
and runs because -SenTest All causes OCUnit to look in the entire
runtime, rather than just classes from your test bundle, and it finds
the SenTestCase subclass SenInterfaceTestCase within
SenTestingKit.framework.
Finally, building tests with Xcode 3.0 isn't expected to hit a
breakpoint in the tests. Only actually debugging an executable will
cause Xcode to hit a breakpoint. This behavior is unchanged from the
OCUnit included with previous versions of Xcode all the way back to
Xcode 2.1.
-- 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