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

Re: crash in mach_msg_trap


  • Subject: Re: crash in mach_msg_trap
  • From: "Martin Redington" <email@hidden>
  • Date: Thu, 25 Sep 2008 18:45:20 +0100

Thanks Ken,

   running directly in the debugger did indeed drop me into the correct thread.

So what I'm seeing here is just a side effect of auto-attach presumably ...

    cheers,
            m.

On Tue, Sep 23, 2008 at 9:50 PM, Ken Thomases <email@hidden> wrote:
> On Sep 22, 2008, at 10:27 PM, Martin Redington wrote:
>
>> I've got an application that crashing regularly, but at different
>> points in my own code. It looks like an issue with a member field
>> getting over-ridden, but that's (possibly) irrelevant to my query.
>>
>> When I run the app from Xcode, it always breaks into gdb with the
>> following stack trace:
>>
>> #0      0x95a694a6 in mach_msg_trap
>> #1      0x95a70c9c in mach_msg
>> #2      0x94a730ce in CFRunLoopRunSpecific
>> #3      0x94a73cf8 in CFRunLoopRunInMode
>> #4      0x90032480 in RunCurrentEventLoopInMode
>> #5      0x90032299 in ReceiveNextEventCommon
>> #6      0x9003210d in BlockUntilNextEventMatchingListInMode
>> #7      0x94ceb3ed in _DPSNextEvent
>> #8      0x94ceaca0 in -[NSApplication
>> nextEventMatchingMask:untilDate:inMode:dequeue:]
>> #9      0x94ce3cdb in -[NSApplication run]
>> #10     0x94cb0f14 in NSApplicationMain
>> #11     0x00002ffc in main at main.m:13
>
> This is almost certainly the backtrace of the wrong thread.  I expect that a
> different thread has crashed.
>
> If you are expecting a crash (and trying to debug it), don't rely on Xcode's
> auto-attach debugger feature.  Run the program in the debugger directly.
>  This will provide you with more accurate debugging information.  First, the
> debugger will state what kind of kernel exception (different than a Cocoa
> exception) or signal was encountered.  Second, it will display the relevant
> thread.
>
> Good luck,
> Ken
>



--
http://www.mildmanneredindustries.com/
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >crash in mach_msg_trap (From: "Martin Redington" <email@hidden>)
 >Re: crash in mach_msg_trap (From: Ken Thomases <email@hidden>)

  • Prev by Date: Re: Find no longer working
  • Next by Date: Attn: Philip Aker
  • Previous by thread: Re: crash in mach_msg_trap
  • Next by thread: Clearing the debugger console
  • Index(es):
    • Date
    • Thread