[PD] crash report

[chris clepper]

At first glance, it appears to be a GUI and not a GEM crash.  However, 
that old GEM cache crash (say that three times really fast) would bail 
at the weirdest points.

cgc

On Jul 7, 2004, at 10:55 PM, doktorp wrote:
> crashlog:
>
>
> Thread 0 Crashed:
> 0   pd                            	0x0001f90c gobj_getrect + 0x10 
> (crt.c:300)
> 1   pd                            	0x00009734 linetraverser_next + 
> 0x194 (crt.c:300)
> 2   pd                            	0x0000acc0 canvas_deletelinesfor + 
> 0x8c (crt.c:300)
> 3   pd                            	0x0000c3c0 glist_delete + 0x11c 
> (crt.c:300)
> 4   pd                            	0x0000e864 graph_delete + 0x44 
> (crt.c:300)
> 5   pd                            	0x0000c3c0 glist_delete + 0x11c 
> (crt.c:300)
> 6   pd                            	0x0000aa34 canvas_free + 0x80 
> (crt.c:300)
> 7   pd                            	0x00037624 pd_free + 0x2c 
> (crt.c:300)
> 8   pd                            	0x000391d8 pd_typedmess + 0x354 
> (crt.c:300)
> 9   pd                            	0x00039318 pd_typedmess + 0x494 
> (crt.c:300)
> 10  pd                            	0x0003c3a8 binbuf_eval + 0x3e4 
> (crt.c:300)
> 11  pd                            	0x00041788 socketreceiver_read + 
> 0x1cc (crt.c:300)
> 12  pd                            	0x000412a0 sys_domicrosleep + 0x140 
> (crt.c:300)
> 13  pd                            	0x0003fa78 m_scheduler + 0x2bc 
> (crt.c:300)
> 14  pd                            	0x00040064 sys_main + 0x1a4 
> (crt.c:300)
> 15  pd                            	0x00008c14 _start + 0x188 
> (crt.c:267)
> 16  dyld                          	0x8fe1a558 _dyld_start + 0x64