Vivek Khera wrote:
>
> > "TB" == Tim Bunce <[EMAIL PROTECTED]> writes:
>
> TB> I recall someone once created a whole bunch of gdb macros for debugging
> TB> perl. I've CC'd this to p5p in the hope that someone remembers.
>
> In the mod_perl source tree (at least in CVS) there's a nice .gdb
> "TB" == Tim Bunce <[EMAIL PROTECTED]> writes:
TB> I recall someone once created a whole bunch of gdb macros for debugging
TB> perl. I've CC'd this to p5p in the hope that someone remembers.
In the mod_perl source tree (at least in CVS) there's a nice .gdbinit
file that may be of use.
--
I recall someone once created a whole bunch of gdb macros for debugging
perl. I've CC'd this to p5p in the hope that someone remembers.
Tim.
On Tue, Feb 06, 2001 at 12:32:45PM -0800, sterling wrote:
> If you're looking for which piece of perl code being processed, there
> are some gdb macros to
Hi again,
On Tue, 6 Feb 2001, Shane Adams wrote:
> I tried the 'man gdb' command and it didn't
> help much I'm afraid...
Then why not have a look at
http://www.gnu.org/manual/gdb-4.17/gdb.html
I'm not a great fan of using debuggers, but as they go it's fantastic,
it's really worth getting to
Title: RE: Debugging mod_perl with gdb
Hey thanks. I'll try this. I tried the 'man gdb' command and it didn't help much I'm afraid...
-Original Message-
From: sterling [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 06, 2001 12:33 PM
To: Shane A
If you're looking for which piece of perl code being processed, there
are some gdb macros to help. If you source the .gdbinit in the root of
your modperl dir you have access to a bunch of cool macros to use. In
this case, curinfo will give you the current line number in your perl
code.
here's t
Hi there,
On Tue, 6 Feb 2001, Shane Adams wrote:
> I've found a "write to a dangling pointer" when apache/mod_perl
> evaluates a section of the apache config file.
>
> My question: How do I go about attacking this problem?
1. Reduce your test case to the absolute minimum.
2. 'perldoc perldeb
