Re: SIGBUS crash in 10.1 (was: studentdev digest...)
Re: SIGBUS crash in 10.1 (was: studentdev digest...)
- Subject: Re: SIGBUS crash in 10.1 (was: studentdev digest...)
- From: "R. Tony Goold" <email@hidden>
- Date: Fri, 5 Oct 2001 17:12:36 -0400
there is no definition for
[NSDocument _handleDocumentFileChanges]
This is probably an internal method.
This is the method that it thinks it is inn when all hell breaks loose,
but there is no sign of it in any of the help docs. If someone as inside
knowledge of why Apple made some fundamental change to the way objects
are handled, and how I can make it behave like it did last time then I'd
really appreciate some input.
My guess is that they discovered a class that was either autoreleasing
when it should have been releasing, or something that simply retained one
time too many. So an object that should have disappeared (due to bugs in
your code) was lucky enough to be kept around when it wouldn't have
normally been retained.
If it doesn't occur until your program finishes drawing itself for the
first time, I wouldn't be surprised if you'd autoreleased (or failed to
retain something created with a convenience constructor; same problem,
different name) something and it didn't get munged until the first time
through the event loop (when the autorelease pool is released).
But I'm very new to ObjC and Cocoa myself, so don't take this as expert
advice :-)
Cheers,
Tony