Re: exited due to signal 10 (SIGBUS).
Re: exited due to signal 10 (SIGBUS).
- Subject: Re: exited due to signal 10 (SIGBUS).
- From: Art Isbell <email@hidden>
- Date: Wed, 25 Jul 2001 13:10:05 -1000
On Wednesday, July 25, 2001, at 12:17 PM, Rosyna wrote:
My Cocoa application always seems to flash the window I am loading from
a nib and then crashes immediately. I have log messages all over and
the are all being called, even after I load the nib and show the
window. I cannot debug the application because it always says the crash
is in NSApplicationMain in the main() function.
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.
My question is, are nibs showing windows done in a thread?
Yes, the main thread, so nothing is happening behind your back in
another thread. Even if it was, the debugger can debug all threads, so
you could determine the answer to your question using the debugger.
The debugger is your friend...
Art Isbell
Apple iServices Technical Support
http://www.apple.com/iservices/webobjectssupport/
+1-808-591-0836