• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
OCUnit question
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

OCUnit question


  • Subject: OCUnit question
  • From: Aldo Bergamini <email@hidden>
  • Date: Thu, 11 Dec 2008 11:07:34 +0100

I have been reading the "Automated Unit Testing with Xcode 3 and Objective-C" tutorial.

It is a very good thing, btw, but I am running into problems with the last (actually very important) point: debugging.

If I do blindly follow the instructions, I get the following error when I try the Debug command:

[Session started at 2008-12-11 10:34:10 +0100.]
Loading program into debugger…
GNU gdb 6.3.50-20050815 (Apple version gdb-962) (Sat Jul 26 08:14:40 UTC 2008)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-apple-darwin".tty /dev/ttys002
Program loaded.
sharedlibrary apply-load-rules all
run
[Switching to process 33282 local thread 0x2d03]
Running…
DevToolsBundleInjection: The XCInjectBundle environment variable must be set with the path of a bundle to inject, in filesystem representation.




My understanding of this $%$^$# is that the argument with name XCInjectBundle is not properly set.



Now in the last hour I have fiddling with a linear combination of values like:

   as indicated                             UnitTests.octest
   in the tutorial

   with added cleverness	     $(BUILT_PRODUCTS_DIR)/UnitTests.octest

   with added dumbness          /Users/aaberga/Documents/Dev/Cocoa/
						     OCT/build/Debug/UnitTests.octest



I have even recreated the additional target, removing the space in the original name (from "Unit Tests" to "UnitTests").

But somehow the debugger is never called, even if the test per se are both compiled and run. I was able to "see the bug", and fix it!...

Can anybody help with this problem? TIA


Needless to say that unit testing without the debugger is relatively pointless, besides from the occasional setup where you know the bug and its location...



Aldo _______________________________________________ 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
  • Follow-Ups:
    • Xcode won't select correct SDK
      • From: Eric Gorouben <email@hidden>
  • Prev by Date: Re: Newbie Question - #include scope
  • Next by Date: Xcode won't select correct SDK
  • Previous by thread: Re: weird things with safe iterators in xcode debug configurations
  • Next by thread: Xcode won't select correct SDK
  • Index(es):
    • Date
    • Thread