Re: Crash in AppKit.subproj/NSViewHierarchyLock.m:444
Re: Crash in AppKit.subproj/NSViewHierarchyLock.m:444
- Subject: Re: Crash in AppKit.subproj/NSViewHierarchyLock.m:444
- From: Aki Inoue <email@hidden>
- Date: Tue, 10 Jan 2006 22:20:36 -0800
Steve,
1. What is causing this?
The most common cause is unmatched -[NSView unlockFocus] invocations.
3. How can I catch assertions in the appkit and handle them myself,
i.e. force a crash which will cause the app to backtrace the
crashed thread (that code is written, I just need to catch the
assertion)?
NSAssertionHandler should raise exception. Probably it's being
caught by one of AppKit's own handlers. You can run the app in gdb
and break at -[NSException raise] the get the backtrace.
Aki
I'm getting this in the console:
*** Assertion failure in -[NSViewHierarchyLock
unlockTopMostReader], AppKit.subproj/NSViewHierarchyLock.m:444
Three questions:
1. What is causing this?
2. How can I prevent it?
3. How can I catch assertions in the appkit and handle them myself,
i.e. force a crash which will cause the app to backtrace the
crashed thread (that code is written, I just need to catch the
assertion)?
One detail, this happens when opening a window which happens on
start up. It's also not consistent.
- Steve _______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden