In the, "I've pulled out all my hair" files... HELP!
Using CodeWarrior 9.6, I've managed to get a new Mach-O target to
cleanly compile and link from our Carbon CFM codebase. However,
during the app initialization phase (after InitCursor()), it crashes
in the Carbon framework (when calling Menu Manager code). If I
change the order of things, it'll crash elsewhere (e.g., on SysBeep
()). Yet, clearly, some Carbon calls work OK (InitCursor(),
UseResFile(), etc.).
I've checked my target's settings against a virgin PowerPlant Mach-O
target (which works as advertised), and can't find anything different
that would cause the problem. I've also checked the built Mach-O app
package against the working CFM one, and can't find anything missing
there either. I've even tried linking against the /System/Frameworks
paths, as well as the 10.3.9 and 10.4.0u SDKs, and get the same results.
And, when I try to use the Carbon.debug variant of the framework -
it'll crash in early init code, rendering that pretty much useless.
Anyone have a clue?
Thanks!
Mark
