Re: Help with debugger (mach_msg_trap) message
Re: Help with debugger (mach_msg_trap) message
- Subject: Re: Help with debugger (mach_msg_trap) message
- From: Jens Alfke <email@hidden>
- Date: Tue, 2 Feb 2010 08:09:14 -0800
On Feb 2, 2010, at 7:36 AM, McLaughlin, Michael P. wrote:
> The Debugger window shows the calling stack at the top of which is
>
> 0 mach_msg_trap
> 1 mach_msg
> 2 CFRunLoopRunSpecific
> etc.
This is showing the main thread, which is just paused waiting for events. The crash is on a different thread, but Xcode 3.1 often doesn't switch to the thread that crashed. You'll need to use the thread pop-up to switch between the different threads to see which one actually has a crash. (Any other threads that are in mach_msg_trap or in various functions having to do with locks or semaphores are also just idling.)
Another way to find the crashed thread is to type "thread apply all bt" at the "(gdb)" prompt, which will dump a backtrace of every thread.
> 2/2/10 10:18:49 AM [0x0-0x1fe1fe].com.apple.Xcode[8765]
> Xcode(8765,0xf0103000) malloc: free_garbage: garbage ptr = 0x3791fa0, has
> non-zero refcount = 1
This is just a harmless error message that's frequently logged by Xcode due to some sort of minor garbage-collection bug. Nothing to do with your app.
—Jens
_______________________________________________
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