Hi Johannes, thanks for your report.
I tried your patch (it's good to give the abs abstraction another name, since abs is an internal object), but everything works as expected both with Miller's PD and with devel_0_39. Not a single valgrind message is generated here (apart from a harmless one from inside pthreads). It seems there's something strange with your system that is beyond my scope. I'm curious about more observations though.
best greetings, Thomas
Johannes Burström wrote:
Hi
Thomas Grill wrote:
If you could use the debug version of pool (built with "flext/build.sh pd gcc build-debug-single") and run pd with valgrind, some helpful information could probably be gathered.
I've tried to make an easy patch to provoke a segfault, and finally found a good recipe... attached is "abs.pd" and "parent.pd". open parent with abs in path, and remove one or two instances of abs, perhaps undo once, and pd will eventually crash.
I compiled a debug version of pool, and did the above with valgrind. output is attached. it's the first time i've run valgrind, so i just ran it without any special arguments.. hope it can be of some use.
thanks, Johannes