FROM : listposter
DATE : Fri Nov 09 18:07:45 2007
Hi,
I recently tried to get my test rig up and running in leopard, and my
framework has been using GC only for a while now.
Setting up a custom executable to call otest on my test bundle,
causese the following error:
2007-11-10 01:54:43.694 otest[26142:813] Error loading /Volumes/Builds/
Debug/MyApplicationKitUnitTest.octest/Contents/MacOS/
MyApplicationKitUnitTest: dlopen(/Volumes/Builds/Debug/
MyApplicationKitUnitTest.octest/Contents/MacOS/
MyApplicationKitUnitTest, 265): no suitable image found. Did find:
/Volumes/Builds/Debug/MyApplicationKitUnitTest.octest/Contents/MacOS/
MyApplicationKitUnitTest: GC capability mismatch
2007-11-10 01:54:43.768 otest[26145:203] *** NSTask: Task create for
path '/Volumes/Builds/Debug/MyApplicationKitUnitTest.octest/Contents/
MacOS/MyApplicationKitUnitTest' failed: 8, "Exec format error".
Terminating temporary process.
2007-11-10 01:54:43.860 otest[26145:203] Usage: otest [-SenTest Self |
All | None | <TestCaseClassName/testMethodName>] <path of unit to be
tested>
2007-11-10 01:54:43.860 otest[26145:203] *** -[NSConcreteTask
terminationStatus]: task not launched
When I compile the framework test unit to use -fobjc instead of -fobj-
c-only testing works as normal.......
Is this known, and if so, is there a workaround? If I have an app, and
want to test a critical section, that uses only GC.... how can I
accomplish that if SenTestingKit is gonna barf every time I throw GC-
Only objects at it?
Any help would be appreciated
Andre
DATE : Fri Nov 09 18:07:45 2007
Hi,
I recently tried to get my test rig up and running in leopard, and my
framework has been using GC only for a while now.
Setting up a custom executable to call otest on my test bundle,
causese the following error:
2007-11-10 01:54:43.694 otest[26142:813] Error loading /Volumes/Builds/
Debug/MyApplicationKitUnitTest.octest/Contents/MacOS/
MyApplicationKitUnitTest: dlopen(/Volumes/Builds/Debug/
MyApplicationKitUnitTest.octest/Contents/MacOS/
MyApplicationKitUnitTest, 265): no suitable image found. Did find:
/Volumes/Builds/Debug/MyApplicationKitUnitTest.octest/Contents/MacOS/
MyApplicationKitUnitTest: GC capability mismatch
2007-11-10 01:54:43.768 otest[26145:203] *** NSTask: Task create for
path '/Volumes/Builds/Debug/MyApplicationKitUnitTest.octest/Contents/
MacOS/MyApplicationKitUnitTest' failed: 8, "Exec format error".
Terminating temporary process.
2007-11-10 01:54:43.860 otest[26145:203] Usage: otest [-SenTest Self |
All | None | <TestCaseClassName/testMethodName>] <path of unit to be
tested>
2007-11-10 01:54:43.860 otest[26145:203] *** -[NSConcreteTask
terminationStatus]: task not launched
When I compile the framework test unit to use -fobjc instead of -fobj-
c-only testing works as normal.......
Is this known, and if so, is there a workaround? If I have an app, and
want to test a critical section, that uses only GC.... how can I
accomplish that if SenTestingKit is gonna barf every time I throw GC-
Only objects at it?
Any help would be appreciated
Andre
| Related mails | Author | Date |
|---|---|---|
| listposter | Nov 9, 18:07 | |
| Chris Hanson | Nov 9, 21:37 | |
| Timothy Reaves | Nov 9, 22:55 | |
| Chris Hanson | Nov 10, 03:19 | |
| listposter | Nov 10, 04:54 |






Cocoa mail archive

