On Sat, 8 May 2010, mark hadman wrote:
pd-ext just completely disappeared on me, twice, while editing
completely different stuff within the space of two hours. Neither error
was easily reproducible (ie going back and doing more or less the same
again didn't crash pd again). If I try the nightly build again I will
run it from a terminal and try to document errors (where - on this
list?),
Try Valgrind to help you detect errors. It makes many invisible errors
visible, and tends to often pinpoint the real cause, instead of the final
consequence. But not all the time (because that's not possible in C/C++).
Then you can cut out the relevant part from the Valgrind report (Invalid
Read or Invalid Write) and include it in the bug report. But it only works
with builds that include debugging-symbols (I don't know which ones those
are).
_ _ __ ___ _____ ________ _____________ _____________________ ...
| Mathieu Bouchard, Montréal, Québec. téléphone: +1.514.383.3801
_______________________________________________
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
