crash in mach_msg_trap
crash in mach_msg_trap
- Subject: crash in mach_msg_trap
- From: "Martin Redington" <email@hidden>
- Date: Tue, 23 Sep 2008 04:27:35 +0100
Slightly OT, but debugging related ...
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
====
0x95a6949c <+0000> mov $0xffffffe1,�x
0x95a694a1 <+0005> call 0x95a69cf4 <_sysenter_trap>
0x95a694a6 <+0010> ret
0x95a694a7 <+0011> nop
====
When I hit continue, I then hit a crash in my own code. I'm still
looking to see where I'm overwriting the member that seems to be
causing the crash, but my queries are:
Why do I always break on the above stack trace immediately before the crash?
Is this diagnostic of anything that might help me track down my actual issue?
--
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