Re: Connect gdb to a running perl process

in reply to Connect gdb to a running perl process

This might be a stupid question, but why are you using gdb to debug your Perl script? Why not invoke the Perl debugger? If you do need to debug using gdb, some of the methodology described at http://modperlbook.org/html/ch21_07.html may be of use.

(By the way, from the where output, I would hazard a guess that your Perl code is executing a sleep statement)

perl -le "print unpack'N', pack'B32', '00000000000000000000001000000000'"

Comment on Re: Connect gdb to a running perl process Select or Download Code

Replies are listed 'Best First'.
Re^2: Connect gdb to a running perl process by saintmike (Vicar) on Feb 14, 2005 at 19:32 UTC
This might be a stupid question, but why are you using gdb to debug your Perl script? Why not invoke the Perl debugger? You can't call the perl debugger on a running perl script, can you? Requirement is to not having to restart the process. (By the way, from the where output, I would hazard a guess that your Perl code is executing a sleep statement) Right, this was a sample script. I was hoping there was a proven sequence of gdb commands to examine perl's internal data structures revealing the current file and line.	[reply]

Replies are listed 'Best First'.

Re^2: Connect gdb to a running perl process
by saintmike (Vicar) on Feb 14, 2005 at 19:32 UTC

This might be a stupid question, but why are you using gdb to debug your Perl script? Why not invoke the Perl debugger?

You can't call the perl debugger on a running perl script, can you? Requirement is to not having to restart the process.

(By the way, from the where output, I would hazard a guess that your Perl code is executing a sleep statement)

Right, this was a sample script. I was hoping there was a proven sequence of gdb commands to examine perl's internal data structures revealing the current file and line.

[reply]

In Section Seekers of Perl Wisdom