Re: Crashes with no backtrace when printing

FROM : Brian Stern
DATE : Fri Jul 04 05:39:29 2008

On Jul 3, 2008, at 7:24 PM, Ben wrote:

> 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
>



What good is a debugger that can't give a stack trace when the app 
crashes?

See this recent thread on xcode_users:

http://lists.apple.com/archives/xcode-users/2008/Jun//msg00735.html

Activity Monitor is your friend.

In the end file a bug report against gdb and the debugger.  Maybe 
they'll fix it.

--
Brian Stern
<email_removed>