if you can reproduce the crash you can use `gdb` to find out which object trigs the crash
it will let you know which external crashes when receiving which message
after that you can make a smaller patch with only the crashing part
and if it is reproducible, don't hesitate to fill a bug report with the patch and the way to reproduce the crash and, if possible, a gdb backtrace
 
see [1] for more details

+
a

[1] : http://puredata.info/docs/developer/DebuggingPdExternals

--
do it yourself                      
http://antoine.villeret.free.fr

2014-09-11 17:51 GMT+02:00 plutek infinity <plutek@infinity.net>:
On 2014-09-11 11:37, Py Fave wrote:
4. what platform are you running on ?
version of pd ?

 0.46.0 ("") on linux.

what does your patch should do?

 it does a lot of things...  :)   filters/resonance, ringmod, harmonization, delay, spectral manipulation, with a patching matrix between all the modules. it's a live performance instrument, manipulating sound from acoustic sources, and with a bunch of MIDI switches and pedals to control parameters.

thanks for all your suggestions, py... it has grown quite complicated over the years, and is probably in need of some housekeeping! i was just hoping there might be a debugging tool which might help point to specific issues.  ;)


cheers!
.pltk.

_______________________________________________
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list