Oops, I should have explained more carefully... I can't get GDB to load symbols from externs. So I can trap into GDB when something goes wrong but then can't see anything.
I usually just compile the object I'm debugging into Pd itself to fix this.
cheers M
On Tue, Nov 14, 2006 at 01:25:50PM +0100, Tim Blechmann wrote:
several ways to debug pd externals with gdb:
- crash the external (with asserts)
- declare pending breakpoint, that are resolved after the shared library
has been loaded
- set breakpoint after the dlopen stuff, when the symbols are available
- break manually after the external has been loaded and the symbols are
available
- use the gdb integration into your favorite ide to set breakpoints in
source files. (should work with about every decent ide like emacs, eclipse, kdevelop)
tim
On Mon, 2006-11-13 at 09:17 -0800, Miller Puckette wrote:
Just to add to the fun... I've NEVER been able to get teh debugger to see Pd externals. I can debug Pd itself on linux and Mac OK. The only thing I've found is that, on Mac, it's important to be sure not to 'debug' the GUI process instead of Pd by accident.
cheers Miller
On Mon, Nov 13, 2006 at 11:12:31AM -0500, james tittle wrote:
On Nov 13, 2006, at 9:59 AM, forwinder wrote:
Still can't get the bugger to set a break point though. GDB was helpfully in that once PD died I could at least the back trace.
...did you compile pd with "-g -O0"? Are you stripping symbols somewhere? What platform are you trying to debug on?
james
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
-- tim@klingt.org ICQ: 96771783 http://www.mokabar.tk
Cheat your landlord if you can and must, but do not try to shortchange the Muse. It cannot be done. You can't fake quality any more than you can fake a good meal. William S. Burroughs
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev