On Mar 25, 2005, at 3:57 PM, Scott T. Hildreth wrote:
Well I compiled the module with -g. I am testing with 'perl -d -e0', just loading the module and stepping into it. When it started to hang, I attached to the process with gdb. About all I could do was get a back trace.
did the backtrace make sense? where did it stop?
I probably really need to compile a version of perl with -g, right?
i debug xs quite often and have not found a debugging perl to be helpful. the perl API is so heavily macro-driven that it's hard to do much in gdb, but for your own code you'll be able to get around easily, and the bug is nearly always in your own code.
Would it help to show the *.c produced by xsupp?
without information on what the function is supposed to do, what it actually is doing, and what the error is, all i can do is say things like "try running it in gdb and/or valgrind".
-- elysse (pregnant): are your hands cold? me: uh, i suppose so. elysse: will you put them on me?
