hi
you can use print to check your values in the console
or print to file
- clean your patches and remove all that is not necessary.
tidy up the wires too .
- try to narrow it by making little modular parts you can test individually
4.try to use as few as possible extras ,replace by abstractions if possible.
- remove as much as possible visual elements.
replace bng by bang , beware of nested gop
check processor usage
- what platform are you running on ?
version of pd ?
what does your patch should do?
- you can open a question topic on a puredata forum
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