Apparently it's something having to do with Python, when a Python script was loaded in the [pyo~] external when the DSP was turned on. Disabling this solved this issue. It's a Python issue and not Pd, sorry for the noise.
On 15/8/21 6:54 μ.μ., Alexandros wrote:
I'm trying to run a patch I've been using for a long time on a Raspberry Pi after applying some changes to it and I get the error in the subject line. After I applied the changes, before I shut down the Pi, the patch run fine. After rebooting the Pi, I keep on getting this error whenever I try to turn on the DSP. Tried adding -noloadbang but I get the same. After this error I get the "watchdog: signaling pd..." message or a crash.
Tried to run this in gdb and this is the output:
[Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1". [Detaching after fork from child process 1131] [Detaching after fork from child process 1133] [New Thread 0x74788460 (LWP 1137)] [Thread 0x74788460 (LWP 1137) exited] [New Thread 0x73dff460 (LWP 1140)] [Thread 0x73dff460 (LWP 1140) exited] liblo server error 9904 in path (null): cannot find free port
Thread 1 "pd" received signal SIGSEGV, Segmentation fault. 0x7546d48c in lo_server_add_method () from /usr/lib/arm-linux-gnueabihf/liblo.so.7
When the crash occurs gdb prints the lines below this (including it): [New Thread 0x73dff460 (LWP 1140)]
The patch is quite big and needs specific hardware to run (Teensy micro-controller, and several peripherals), so I don't know if it makes sense to share it, since reproducing this error would probably require all the hardware. I know my question is rather vague, but that's all I can share right now. I'm running Pd-0.50.2 on Raspbian Buster.