I have a Carbon application that has been working fine under Tiger, but after upgrading to Leopard, the application is crashing in some Objective-C message sends. This problem occurs on a dual G5 and not on an Intel iMac.
It appears the message that crashes is being sent to a NULL pointer from a series of message sends relating to display updates. The messages are being sent from the Carbon message dispatcher. (Another odd thing is that the crash occurs only after closing a file that has just been written by my application.)
When the application is on the Intel iMac, all of the threads are C threads. On the dual G5, I am seeing some threads that are sending Objective-C messages.
I am trying to figure out why there are *any* Objective-C messages, since this is a Carbon-only application and never makes any Cocoa calls.
Any clues as to what may be happening to cause the crash? Or why there are Objective-C Cocoa messages being sent by my app?
-Konrad
_______________________________________________
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
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/email@hidden
This email sent to email@hidden
