Re: Signal error 10 and 11 in PB
Re: Signal error 10 and 11 in PB
- Subject: Re: Signal error 10 and 11 in PB
- From: "R. Tony Goold" <email@hidden>
- Date: Sun, 15 Jul 2001 18:11:01 -0400
Without more information it's hard to say, but I'd guess what's happening
is that some piece of information related to the GUI is being autoreleased.
As long as the window is showing it doesn't need to refetch the data, but
when you switch to another window and come back that forces an update and
it attempts an illegal memory access.
With the debugger you may be hitting that update condition earlier.
Make sure you aren't forgetting to retain any objects created with
convenience constructors.
Cheers,
Tony
On Sunday, July 15, 2001, at 05:34 , Michel Haver wrote:
Working with my project in ProjectBuilder resulted in the following
conflict
If I switch between two Windows and back again, the application crashes
with error: Test.app has exited due to signal 11 (SIGSEGV).
Build and Run succeed will succeeded, but after the switch between two
Windows the application crashes.
If you try to debug the problem by Build and Debug you get after the
message
Reading symbols for shared libraries .... done
The Debugger has exited due to signal 10 (SIGBUS).
If you look up the information about these signals you find:
Name Default Action Description
SIGBUS create core image bus error
SIGSEGV create core image segmentation violation
Why can't I use the debugger any more to trace the conflict I am getting?
Tooltip?
Cheers,
Michel
_______________________________________________
cocoa-dev mailing list
email@hidden
http://www.lists.apple.com/mailman/listinfo/cocoa-dev