I have just been getting my app to print two custom views. One uses a
layer-backed NSView (many CALayer sublayers, in the region of 450-
ish), one a plain NSView. Sometimes (rarely, but often enough), with
no apparent pattern, the app is crashing just before showing the print
dialog. The problem is that the backtraces I get are more or less as
follows :
Attaching to program: `/Path/goes/here', process 14859.
Cannot access memory at address 0x9ead7
Cannot access memory at address 0x9ead7
(gdb) bt
#0 0x0009ead3 in ?? ()
#1 0x0018ee80 in ?? ()
Cannot access memory at address 0x9ead7
A crashlog in the console said the following:
"image not found for lazy pointer at 0x973f014"
My debugging skills are not good enough to know how to work around
this and find the source of the crash. I have GC enabled and
originally thought than some required object was being collected, but
after maintaining strong references to all the objects I use and it
still happens, I'm not sure that's it.
The reason I thought having GC enabled may be the source is that these
crashes are often accompanied by messages warning of collected objects
having a non-zero refcount. I'm pretty certain these objects aren't
ones I've personally allocated.
Anyway, that's all the pertinent info I can think of. Does anyone have
any suggestions about how to start tracing the cause of these crashes?
Regards,
Ben
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
