| So using Xcode 3.0, a debug build results in the following gdb error log when run (no warnings/errors when linking) on a G5 (haven't tried a debug build on x86 yet):
run [Switching to process 8300 local thread 0x2e1b] Running… dyld: Library not loaded: /System/Library/Frameworks/CoreServices.fram\340 Referenced from: /Volumes/YWork4/Dominogy/build/Debug/Dominogy.app/Contents/MacOS/Dominogy Reason: image not found Program received signal: “SIGTRAP”. Xcode: Introspection dylib not loaded because thread 1 has function: __dyld_dyld_fatal_error on stack warning: Couldn't find minimal bounds for "_sigtramp" - backtraces may be unreliable
If I examine the mach-o file with otool -l, I find the following:
Load command 12 cmd LC_LOAD_DYLIB cmdsize 100 name /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices (offset 24) time stamp 2 Wed Dec 31 18:00:02 1969 current version 18.0.0 compatibility version 1.0.0
so that looks good. Doing a "Release" build works fine as well (but obviously harder to debug). I've done a complete "clean all" (including cleaning pre-compiled headers) and that doesn't change anything.
The release version (PPC part) has:
Load command 12 cmd LC_LOAD_DYLIB cmdsize 100 name /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices (offset 24) time stamp 2 Wed Dec 31 18:00:02 1969 current version 16.0.0 compatibility version 1.0.0
Turns out that my sdkroot_PPC was "/Developer/SDKs/MacOSX10.3.9.sdk" for release, and not set for debug. Setting debug sdk to 10.3.9 results in getting version 18.0.0 in the LC_LOAD_DYLIB command (to match the release version) but the same crash.
Any suggestions on how to further track this down?
Dominogy | Just place all the dominos on the board... |