greetings!
the question:
is there a way to make pd tell me specifically what part of a patch is causing a crash, so i can identify the problem and fix it? the debug command-line option doesn't seem to give useful results for my current issue.
background:
i have a patch which is significantly complicated, including many subpatches, etc... it used to run just fine, but has recently started crashing when i click on some toggles in my interface. however, it's not always the same toggle that causes the crash, nor is it a reliable number or group of toggles, as far as i can tell.
there was one message which was supposed to be received by a toggle, but which wasn't being received the last time i opened the patch. i fixed that error, and saved the patch. however, the crashing was happening both before and after that fix, so i'm afraid some other little things in the coding may have changed somehow. don't know how that could have happened, but anyways....
many thanks in advance... cheers! .pltk.
hi
you can use print to check your values in the console
or print to file
tidy up the wires too .
4.try to use as few as possible extras ,replace by abstractions if possible.
replace bng by bang , beware of nested gop
check processor usage
version of pd ?
what does your patch should do?
6.you can join little patches for people to test.
some problems can be tricky , but you have almost always a workaround.
enjoy :-)
py
2014-09-11 17:06 GMT+02:00 plutek infinity plutek@infinity.net:
greetings!
the question:
is there a way to make pd tell me specifically what part of a patch is causing a crash, so i can identify the problem and fix it? the debug command-line option doesn't seem to give useful results for my current issue.
background:
i have a patch which is significantly complicated, including many subpatches, etc... it used to run just fine, but has recently started crashing when i click on some toggles in my interface. however, it's not always the same toggle that causes the crash, nor is it a reliable number or group of toggles, as far as i can tell.
there was one message which was supposed to be received by a toggle, but which wasn't being received the last time i opened the patch. i fixed that error, and saved the patch. however, the crashing was happening both before and after that fix, so i'm afraid some other little things in the coding may have changed somehow. don't know how that could have happened, but anyways....
many thanks in advance... cheers! .pltk.
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On 2014-09-11 11:37, Py Fave wrote:
- 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.
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:
- 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