Comments on: Tracing Unit Tests with the XCode 3 Debugger

By: Elise van Looij

Elise van Looij — Thu, 28 Jan 2010 20:36:29 +0000

@Max, your problem seems to stem from non-matching build settings. To match them, double-click on each target to bring up the Target Info and click on the Build tab. You can arrange the windows next to each other and scroll through them, comparing the settings. As far as garbage collection goes, “Supported” is the most flexible option.

By: cms

cms — Sun, 15 Nov 2009 13:39:16 +0000

@Max – cool ! I made a previous post about that problem too

http://beatworm.co.uk/blog/computers/smartypants-ides-considered-harmful/

XCode is improving all the time, and it does have some nice features.

I’m afraid I’ve not used Visual Studio ( Visual C++ even) since around, maybe 1996, I really hated it back then! Software sucks.

By: Max Hillaert

Max Hillaert — Sun, 15 Nov 2009 13:24:44 +0000

Found it: Needed to turn off ‘Lazy Loading’ of symbols in the xcode preferences. Working in xcode for the past year, really makes me appreciate Visual Studio at my day job!

By: Max Hillaert

Max Hillaert — Sun, 15 Nov 2009 13:17:48 +0000

@cms: yes I have done that.

By: Max Hillaert

Max Hillaert — Sun, 15 Nov 2009 13:17:02 +0000

I removed UIKit framework from the ‘other linker flags’ setting in my test configuration. Now the problem is that even though otest will run my tests it will not break at my breakpoint. Are there other configuration settings I need to specify? How do I go about solving this problem?

By: cms

cms — Sun, 15 Nov 2009 13:11:08 +0000

@Max

Have you tried explicitly setting the OBJC_DISABLE_GC for the otest executable in it’s inspector ? ( see comments #1 and #2 from @Quinn and @nicolas )

By: Max Hillaert

Max Hillaert — Sun, 15 Nov 2009 13:04:16 +0000

I’m getting this output:

GC: forcing GC OFF because OBJC_DISABLE_GC is set

Error loading /Users/myname/Projects/MyProject/build/Debug-iphonesimulator/Tests.octest/Tests: dlopen(/Users/myname/Projects/MyProject/build/Debug-iphonesimulator/Tests.octest/Tests, 265): Library not loaded: /System/Library/Frameworks/UIKit.framework/UIKit
Referenced from: /Users/myname/Projects/MyProject/build/Debug-iphonesimulator/Tests.octest/Tests
Reason: image not found

The test bundle at Tests.octest could not be loaded because its Objective-C runtime information does not match the runtime information required by the test rig. This is likely because the test rig is being run with Objective-C garbage collection disabled, but the test bundle requires Objective-C garbage collection. To enable Objective-C garbage collection for the test rig, run it in an environment without the OBJC_DISABLE_GC environment variable.
*** NSTask: Task create for path ‘/Users/maxhillaert/Projects/MyBookShelf/build/Debug-iphonesimulator/Tests.octest/Tests’ failed: 8, “Exec format error”. Terminating temporary process.
2009-11-15 12:55:55.610 otest[13234:203] Usage: otest [-SenTest Self | All | None | ]
2009-11-15 12:55:55.612 otest[13234:203] *** -[NSConcreteTask terminationStatus]: task not launched

By: UIKIt requires garbage collection? Huh? - iPhone Dev SDK Forum

UIKIt requires garbage collection? Huh? - iPhone Dev SDK Forum — Wed, 15 Jul 2009 00:41:27 +0000

[...] the OBJ_DISABLE_GC environment variable to YES in the otest executable info window". beatworm.co.uk Blog Archive Tracing Unit Tests with the XCode 3 Debugger __________________ ~~ DO NOT EAT THE NEWBIES ~~ Intro to objective C and When to retain + [...]

By: cms

cms — Fri, 10 Apr 2009 21:48:56 +0000

@Mark – grepping through the shell scripts in /Developer/Tools/ that are normally used to run otest for unit test targets might be illuminating. It looks to me like they use the arch command directly to invoke otest, picking up the architectures to test for from XCode via several environment variables, or falling back to the default system architecture, derived by running ‘arch’ with no arguments.

I don’t think you can use the ‘arch’ utility in the same way, because you need otest to be he executable so that you can debug it as it runs your classes. But setting the value of ARCHPREFERENCE in the otest environment to your default architecture might suffice.

By: cms

cms — Fri, 10 Apr 2009 21:20:14 +0000

@Mark – I’m not sure. It seems like the test bundle isn’t loading because otest doesn’t have an architecture specified (Unknown). You can set an environment variable ARCHPREFERENCE to specify a preferred binary architecture for your system – perhaps setting this in the environment section of the arguments tab for otest to an appropriate value for the architecture you’re trying to debug ? Valid values are documented in the man page for the ‘arch’ command.