How to debug a Perl extension?
From: kj (socyl_at_987jk.com)
Date: 04/24/04
- Next message: Ray Zimmerman: "[ANNOUNCE] SPOPSx::Ginsu (inheritance for SPOPS)"
- Previous message: Chirath Fernando: "Downloading win32 modules for 5.8"
- Next in thread: Tassilo v. Parseval: "Re: How to debug a Perl extension?"
- Reply: Tassilo v. Parseval: "Re: How to debug a Perl extension?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sat, 24 Apr 2004 12:56:46 +0000 (UTC)
I'm trying to track down an apparent bug in a large Perl extension
module called XML::Xerces. This extension links to a library
libxerces-c.so.23, coded in C++.
The bug occurs during a call to one of the functions defined in
libxerces-c.so.23 and I would like to step into that call. I've
heard that it is possible to do this, in one compiles all the
relevant binaries with the right debugging flagsi (see below), but
I'm not really sure if this is enough. I could use some pointers
here.
Anyway, I compiled both libxerces-c.so.23 as well as the binaries
for XML::Xerces using the '-g' flag, installed the libraries, and
fired up the debugger (DB) as usual. I advanced the execution up
to the problematic function call, but when I tried to step into it
(using 's'), the debugger stepped right over it, as if I had hit
'n' instead of 's'. In other words, it behaved as it always did
when encountering a call to a function not written in Perl.
Is there anything else I must do to be able to step into C++ code?
Thanks!
kj
-- NOTE: In my address everything before the period is backwards.
- Next message: Ray Zimmerman: "[ANNOUNCE] SPOPSx::Ginsu (inheritance for SPOPS)"
- Previous message: Chirath Fernando: "Downloading win32 modules for 5.8"
- Next in thread: Tassilo v. Parseval: "Re: How to debug a Perl extension?"
- Reply: Tassilo v. Parseval: "Re: How to debug a Perl extension?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|