Re: exited due to signal 10 (SIGBUS).
Re: exited due to signal 10 (SIGBUS).
- Subject: Re: exited due to signal 10 (SIGBUS).
- From: Rosyna <email@hidden>
- Date: Wed, 25 Jul 2001 16:57:16 -0700
Steps out of my functions completely, then starts doing something
else, which I have provided the backtrace for:
(gdb) bt
#0 0x73f2495c in aeSuspendTheCurrentEvent ()
#1 0x73f24318 in aeResumeTheCurrentEvent ()
#2 0x73f22010 in aeReallyProcessAppleEvent ()
#3 0x73f21ae8 in aeProcessAppleEvent ()
#4 0x737dd600 in AEProcessAppleEvent ()
#5 0x70d75b48 in _DPSNextEvent ()
#6 0x70d756e8 in -[NSApplication
nextEventMatchingMask:untilDate:inMode:dequeue:] ()
#7 0x70d7546c in -[NSApplication run] ()
#8 0x70d9799c in NSApplicationMain ()
#9 0x00003e24 in main (argc=1, argv=0xbffffd3c) at
main.m:19/Users/rosyna/MyFirstProject/
#10 0x00003d18 in _start ()
#11 0x00003b58 in start ()
Ack, at 7/25/01, Art Isbell said:
All crashes occur in NSApplicationMain() because that's the
function invoked from the process entry point, main(). You say that
you have log messages that are being invoked, so that indicates that
your custom code is being invoked before the crash. (Why are you
using log messages instead of debugger breakpoints?) This suggests
that the crash may be occurring within one of your custom methods.
Does the stack backtrace include any of your custom methods? If so,
the custom method with the lowest stack frame number would allow you
to check the state of various variables at the time of the crash.
But if the crash is occurring after your custom methods have
returned, then an examination of the entire backtrace might shed
some light on the problem. Please post this backtrace.
--
Sincerely,
Rosyna Keller
Technical Support/Holy Knight/Always needs a hug
Unsanity: Unsane Tools for Insane People