• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Posting NSApplicationDidFinishLaunchingNotification fails, Application crashes on Intel Macs
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Posting NSApplicationDidFinishLaunchingNotification fails, Application crashes on Intel Macs


  • Subject: Posting NSApplicationDidFinishLaunchingNotification fails, Application crashes on Intel Macs
  • From: Stefan Heukamp <email@hidden>
  • Date: Tue, 31 Jul 2007 08:34:21 +0200

Hi,

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

Thread 0 Crashed:
0 libobjc.A.dylib 0x90a594c0 objc_msgSend + 16
1 com.apple.Foundation 0x927ec17b _nsnote_callback + 230
2 com.apple.CoreFoundation 0x908563e6 __CFXNotificationPost + 345
3 com.apple.CoreFoundation 0x9084dbd1 _CFXNotificationPostNotification + 600
4 com.apple.Foundation 0x927e4724 -[NSNotificationCenter postNotificationName:object:userInfo:] + 121
5 com.apple.Foundation 0x927eb6c9 -[NSNotificationCenter postNotificationName:object:] + 55
6 com.apple.AppKit 0x93274e94 -[NSApplication _postDidFinishNotification] + 124
7 com.apple.AppKit 0x93274d7e -[NSApplication _sendFinishLaunchingNotification] + 67
[...]
18 com.apple.AppKit 0x9326bddb -[NSApplication run] + 512
[...]


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

_______________________________________________

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:
This email sent to email@hidden


  • Follow-Ups:
    • Re: Posting NSApplicationDidFinishLaunchingNotification fails, Application crashes on Intel Macs
      • From: Nick Zitzmann <email@hidden>
  • Prev by Date: NSPropertyListSerialization from a subthread
  • Next by Date: Re: Posting NSApplicationDidFinishLaunchingNotification fails, Application crashes on Intel Macs
  • Previous by thread: NSPropertyListSerialization from a subthread
  • Next by thread: Re: Posting NSApplicationDidFinishLaunchingNotification fails, Application crashes on Intel Macs
  • Index(es):
    • Date
    • Thread