I have a very strange problem. I have built a universal binary for
my application and on my machine (ppc) this just runs fine. On
another machine (Mac Book Pro) the application crashes on startup.
Here is the part of the crash log that seems to be interesting:
Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_INVALID_ADDRESS (0x0001) at 0xba0cc4a3
I have a quit long initialization procedure that is the
applicationDidFinishLaunching: delegate of NSApplication. This
seems to run without an error up to the end (on intel and ppc).
The NSApplicationDidFinishLaunchingNotification is posted (at
least at my ppc) right after the delegate returns.
In the above stack trace it seems to me that this posting fails on
the intel machine. But what is it that can fail with this posting?
I did not register any Observer for this Notification. And why
does this fail on the intel machine and not on the ppc machine.
This is the first time I analyse such a crash log. So I'm not sure
what
KERN_INVALID_ADDRESS (0x0001) at 0xba0cc4a3 means. Does that mean
that the code at address 0xba0cc4a3 should be executed but this is
not a valid address?
Thanks for any help,
Stefan
Try running with NSZombiesEnabled and CFZombieLevel.
- Chris
That does not change anything. No crashes, exceptions, additional
logs at my ppc-Version. Is there a possibility to enable
CFZombieLevel from within the code?
Stefan
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com