Eclipse/EPIC/PadWalker Perl debugging on Windows platform.

Anonymous Monk has asked for the wisdom of the Perl Monks concerning the following question:

I've been unable to get the Eclipse/EPIC/PadWalker combination to debug Perl code on my Windows box. I have a similar setup that works in Linux but for some reason Windows has been giving me fits.

Configuration details
Windows => XP Profession SP 3
Perl => Strawberry v5.12.3
Eclipse => Helios Service Release 2
Epic => 0.5.46
PadWalker => 1.9.2

My test code.

#! /usr/bin/perl

use PadWalker;
PadWalker::bootstrap();
print eval { require PadWalker; PadWalker->VERSION(0.08)} . "\n";
$var = "example text";
print "The \$var contains \"$var\"\n";
[download]

The code completes as expected with the output as shown below.

1.92
The $var contains "example text"
[download]

I placed the PadWalker routines in the source just to ensure that it was installed successfully.

When I start the debugging session the only value displayed in the variables window is "^RE_TRIE_MAXZBUF" with a value of 65536. When I pause the program at the second print statement I was expecting to see the contents $var. The only thing showing is the above mentioned variable.

I have run this same example code in my Linux environment with the results that I expected. The Eclipse/EPIC/PadWalker versions are the same between the two systems. The Perl version on Linux is v5.8.8 and the Linux is RedHat 2.6.18-238.5.1.el5 if that matters.

I've done a couple of days of googling without really finding anything specific. I'm kind of at a loss and was hoping someone else has another perspective.

Thanks

Comment on Eclipse/EPIC/PadWalker Perl debugging on Windows platform. Select or Download Code

Replies are listed 'Best First'.
Re: Eclipse/EPIC/PadWalker Perl debugging on Windows platform. by Anonymous Monk on Jun 14, 2011 at 16:59 UTC
I will follow up with my own posts in the hope that someone else in the future may find it useful. I ran some test code through the my debug configuration that did show the value of the variables. The difference is that all of the variables were declared local by the explicit use of the "my" keyword. Once a variable is declared with the "my" keyword id shows up in the variable list of Eclipse. I should point out that my Linux configuration does not have the same limitation and will show the value of all variables. At least now I have a work around.	[reply]

Replies are listed 'Best First'.

Re: Eclipse/EPIC/PadWalker Perl debugging on Windows platform.
by Anonymous Monk on Jun 14, 2011 at 16:59 UTC

I will follow up with my own posts in the hope that someone else in the future may find it useful. I ran some test code through the my debug configuration that did show the value of the variables. The difference is that all of the variables were declared local by the explicit use of the "my" keyword. Once a variable is declared with the "my" keyword id shows up in the variable list of Eclipse. I should point out that my Linux configuration does not have the same limitation and will show the value of all variables. At least now I have a work around.

[reply]