[PD] [PD-dev] Troubleshooting suggestions
hans at eds.org
Wed Dec 5 01:48:02 CET 2007
I think it's only needed to send this to one list, since many people
are subscribed to both, etc.
There aren't too many things that cause crashes in Pd, so you can try
to known crashers first. That stacktrace seems to say the crash is
in drawing a object to the canvas, or perhaps something GOP.
I would do the equivalent of a stacktrace. So break the connections
at the top of the subpatch that is crashing, then run it, see if it
crashes. Re-attach, then break further down the patch, until you can
pinpoint where the crash is.
Another thing to look for is [until] crashes.
On Dec 4, 2007, at 6:16 PM, Mike McGonagle wrote:
> Hello all,
> I have a patch that has started to cause a crash in PD. In trying
> to figure out exactly what is happening, I reworked the patch, and
> now each of the smaller chunks of code are in their own subpatch.
> So, now the patch doesn't ALWAYS crash. Now the only time it
> crashes is when I open the subpatch containing the offending code,
> BUT only after that code has been executed at least once.
> Lets see if I can give an outline...
> 1. Open the patch.
> 2. Setup the patch for operation.
> 3. Call the subpatch that appears to be cause trouble. Everything
> executes properly and does what it is supposed to do.
> 4. Open the subpatch that contains the troublesome code, and PD
> crashes before it can display the patch.
> I have checked this in several different versions of PD, from the
> nightly builds (ranging from 1129 back to 0927), as well as the 39
> extended version. And all of them crash in the same way.
> This is the first time I have run into something like this, and I
> am not sure how to proceed in troubleshooting this problem. I
> looked at the stack traces in the logs, and everything appears to
> be PD code that is executing.
> Thread 0 Crashed:
> 0 pd 0x0003cbb0 obj_noutlets + 16
> 1 pd 0x0000ca0c glist_drawiofor + 76
> 2 pd 0x0000d030 text_drawborder +
> 976 (g_text.c:1314)
> 3 pd 0x0000d3ac text_vis + 156
> 4 pd 0x0001eca0 gobj_vis + 352
> 5 pd 0x00003eb0 canvas_map + 128
> 6 pd 0x0003b0d4 pd_typedmess + 1092
> 7 pd 0x0003b23c pd_typedmess + 1452
> 8 pd 0x0003f020 binbuf_eval + 1104
> 9 pd 0x00045c70 socketreceiver_read
> + 640 (s_inter.c:542)
> 10 pd 0x000444dc sys_domicrosleep +
> 316 (s_inter.c:182)
> 11 pd 0x00042850 m_scheduler + 1248
> 12 pd 0x00044240 sys_main + 1440
> 13 pd 0x00002174 _start + 340 (crt.c:272)
> 14 pd 0x0000201c start + 60
> I am running on a Mac OS X 10.4.11, while not all of the crashes
> give the exact same stack trace, this is the most prevalent one.
> Peace may sound simple—one beautiful word— but it requires
> everything we have, every quality, every strength, every dream,
> every high ideal.
> —Yehudi Menuhin (1916–1999), musician
> PD-dev mailing list
> PD-dev at iem.at
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pd-list