I have a patch that keeps crashing. (Pd usually doesn't crash.)

I suspect an external, but I'd need a stack trace to prove it.

I am familiar with the basics of gdb (Linux) but... does the Pd binary have debugging symbols? Any gotchas here?

hjh

When something like this happens to me, I usually start with the -noloadbang flag in Pd. It has proved to be rather helpful in such situations, as a crash on start up is most of the times triggered by something that is banged on load.

It's not a crash on startup.

hjh

Yeah, sorry, I meant a crash when you open a patch.

@ddw_music the main distro of pd should not be compiled w/ debugging symbols. I think some distros like debian have versions w/ debugging symbols. (of course you can always compile yourself with --enable-debug as an argument to configure)
https://wiki.debian.org/HowToGetABacktrace

Actually, the crash is after deleting an object in a specific configuration.

I'm running a local build, not a debian download -- later, I tried the reproducer in Windows (no crash) and the older Ubuntu distribution version (no crash). So I guess it's a build issue... if so, I can just leave it at that.

Thanks for the tips --
hjh

@ddw_music I doubt a build issue could make it crash. was it a number box or an object w/ a number box? bc there was recently a bug that was fixed regarding numberboxes crashing pd when deleted

@seb-harmonik.ar said:

was it a number box or an object w/ a number box? bc there was recently a bug that was fixed regarding numberboxes crashing pd when deleted

Coincidentally enough, it was a number box. It's almost certainly that known issue, then. Thanks!

hjh