• 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
RE: Cocoa called from Carbon, objc_msgSend crash in 10.3.9.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Cocoa called from Carbon, objc_msgSend crash in 10.3.9.


  • Subject: RE: Cocoa called from Carbon, objc_msgSend crash in 10.3.9.
  • From: "Matt Fox-Wilson" <email@hidden>
  • Date: Thu, 21 Dec 2006 15:55:31 +1300

I accidentally turned on deplyoment processing for the build so the stack
looks a little odd. The Cocoa call is being made after main(), after
NSApplicationLoad, and during the interface initialisation process of the
application (an internal process rather than a standard Cocoa app process).
There were other entries too, I just didn't want to paste them all.

Interestingly, the user did report a similar problem he'd had in the past
that seemed to relate to fonts (my original research to see if anyone had
experienced this found some notes on font problems) but he says repeating
the process that fixed it for the other app (I think it was Safari) didn't
work this time. I think it's time for me to get him to do some
troubleshooting :)

Thanks for all the ideas.

- Matt Fox-Wilson
- email@hidden


> -----Original Message-----
> From: Marcel Weiher [mailto:email@hidden]
> Sent: Thursday, 21 December 2006 3:11 p.m.
> To: Matt Fox-Wilson
> Cc: email@hidden
> Subject: Re: Cocoa called from Carbon, objc_msgSend crash in 10.3.9.
>
>
> On 18 Dec 2006, at 19:52, Matt Fox-Wilson wrote:
>
> > Thread 0 Crashed:
> > 0   libobjc.A.dylib                0x908611ec objc_msgSend + 0xc
> > 1   com.AmbientDesign.ArtRage2     0x0018929c 0x1000 + 0x18829c
> > 2   com.AmbientDesign.ArtRage2     0x0010e564 0x1000 + 0x10d564
> > 3   com.AmbientDesign.ArtRage2     0x000cf508 0x1000 + 0xce508
> > 4   com.AmbientDesign.ArtRage2     0x00138794 0x1000 + 0x137794
> > 5   com.AmbientDesign.ArtRage2     0x0002af5c 0x1000 + 0x29f5c
> > 6   com.AmbientDesign.ArtRage2     0x002da3a8 0x1000 + 0x2d93a8
> > 7   dyld                           0x8fe17754
> > call_module_initializers_for_objects + 0x1ac
> > 8   dyld                           0x8fe1721c
> > call_module_initializers +
> > 0x40
>
> That stack trace worries me:  is this getting called as a
> result of initializers and before main()?
>
> This may not be a good time to rely on Cocoa.
>
> Marcel
>

_______________________________________________

Cocoa-dev mailing list (email@hidden)

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: Cocoa called from Carbon, objc_msgSend crash in 10.3.9.
      • From: Scott Ribe <email@hidden>
    • Re: Cocoa called from Carbon, objc_msgSend crash in 10.3.9.
      • From: "Shawn Erickson" <email@hidden>
References: 
 >Re: Cocoa called from Carbon, objc_msgSend crash in 10.3.9. (From: Marcel Weiher <email@hidden>)

  • Prev by Date: Modifying an object managed by NSArrayController
  • Next by Date: RE: Using NSAlert Sheets
  • Previous by thread: Re: Cocoa called from Carbon, objc_msgSend crash in 10.3.9.
  • Next by thread: Re: Cocoa called from Carbon, objc_msgSend crash in 10.3.9.
  • Index(es):
    • Date
    • Thread