• 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: Understanding Application crash
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Understanding Application crash


  • Subject: Re: Understanding Application crash
  • From: Appa Rao Mulpuri <email@hidden>
  • Date: Tue, 25 Mar 2014 05:48:48 +0000
  • Thread-topic: Understanding Application crash

Thanks for the reply Jens.




On 3/25/14 11:06 AM, "Jens Alfke" <email@hidden> wrote:

>
>On Mar 24, 2014, at 10:25 PM, Appa Rao Mulpuri <email@hidden>
>wrote:
>
>> What is the best way to understand the Cocoa application crashes?  Some
>>times my application is getting crashed, while clicking on the
>>NSButtons, but it is not always and very rarely. It is happening in the
>>production, not in the staging environment.
>
>Well, look at what¹s in the backtrace:
>
>> 0   CoreFoundation                      0x00007fff8a866b06
>>__exceptionPreprocess + 198
>> 1   libobjc.A.dylib                     0x00007fff8e2ba3f0
>>objc_exception_throw + 43
>> 2   CoreFoundation                      0x00007fff8a8faf49
>>-[NSException raise] + 9
>
>It¹s throwing an exception. Somewhere else in the crash report it should
>say what type of exception it is.
Exception type is:

ERROR 2014-03-22 08:21:59 +0530 An uncaught exception occured
Name: NSUncaughtSystemExceptionException
Reason: Uncaught system exception: signal 11



>
>> 4   libsystem_c.dylib                   0x00007fff8770394a _sigtramp +
>>26
>> 5   ???                                 0x0000000000000000 0x0 + 0
>> 6   AppKit                              0x00007fff8d3ed7b7 -[NSControl
>>sendAction:to:] + 85
>
>Since the exception is triggered by a control sending its action, the
>problem is likely that the object that¹s the target of the control got
>deallocated.

Agreed, Since this exception is getting rarely. Do we have any provision
to extend the stack trace to print in which method the object is getting
deallocated in our class?

>
>‹Jens

This email and any attachments are confidential, and may be legally privileged and protected by copyright. If you are not the intended recipient dissemination or copying of this email is prohibited. If you have received this in error, please notify the sender by replying by email and then delete the email completely from your system. Any views or opinions are solely those of the sender. This communication is not intended to form a binding contract unless expressly indicated to the contrary and properly authorised. Any actions taken on the basis of this email are at the recipient's own risk.

_______________________________________________

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: Understanding Application crash
      • From: Fritz Anderson <email@hidden>
    • Re: Understanding Application crash
      • From: Jens Alfke <email@hidden>
  • Prev by Date: Understanding Application crash
  • Next by Date: Re: Understanding Application crash
  • Previous by thread: Understanding Application crash
  • Next by thread: Re: Understanding Application crash
  • Index(es):
    • Date
    • Thread