Re: Crashes with no backtrace when printing

2008-07-04 Thread Ben
Thanks for the tips Brian Jen, using them I've now found that when the app crashes, there is a reference count underflow somewhere: MyApp(15221,0xb0103000) malloc: reference count underflow for 0x14d6220, break on auto_refcount_underflow_error to debug. Using the breakpoint above in the

Re: Crashes with no backtrace when printing

2008-07-04 Thread Ben
Thanks for the tips Brian Jen, using them I've now found that when the app crashes, there is a reference count underflow somewhere: MyApp(15221,0xb0103000) malloc: reference count underflow for 0x14d6220, break on auto_refcount_underflow_error to debug. Using the breakpoint above in the

Crashes with no backtrace when printing

2008-07-03 Thread Ben
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

Re: Crashes with no backtrace when printing

2008-07-03 Thread Jens Alfke
On 3 Jul '08, at 4:24 PM, Ben wrote: Attaching to program: `/Path/goes/here', process 14859. Cannot access memory at address 0x9ead7 Cannot access memory at address 0x9ead7 I've found that gdb-in-Xcode is more reliable at being able to get a backtrace if you launch the program with the