Hi Dan,
if you're accidentally writing beyond the stack, then the backtrace becomes useless. You can notice this by looking at the function addresses/names. If they have low addresses like 0x9 or don't show a name (although Pd is built with debug symbols), than this is strong indication for a stack overflow. Sometimes GDB will detect a stack overflow.
Two things you can do: 1) set appropiate breakpoints in the debugger to find out where it crashes 2) good ol' printf-debugging :-)
I'm currently working on a complicated external and I highly appreciate the visual debugging tools IDEs like QtCreator give me.
Maybe you can post the stacktrace?
Christof
On 08.02.2020 09:57, Dan Wilcox wrote:
Howdy all,
I've been working on an update to Pd's sound file handling. There is a bug with 32 bit file playback which causes an immediate crash when DSP is on. The backtrace is not very helpful as it just unwinds Pd's main DSP loop.
Are there any tricks to help debug this situation?
Dan Wilcox @danomatika http://twitter.com/danomatika danomatika.com http://danomatika.com robotcowboy.com http://robotcowboy.com
Pd-dev mailing list Pd-dev@lists.iem.at https://lists.puredata.info/listinfo/pd-dev