Problems of EPIC Debugger

andyforpearl wrote on Tue Dec 14 11:46:07 CET 2004:
im using ActivePerl v5.8.4, J2SE v1.4.2_06 SDK, eclipse 3.0 and EPIC 0.3.0
on my Win2000 SP4, Java and Eclipse work fine, but EPIC Perl debugger does
not work, whenever i launch the debugger following error messages appear.
Unable to connect to remote host: 192.168.1.x:5000
Compilation failed in require.
main::BEGIN() called at C:/Perl/lib/ line 0
eval {...} called at C:/Perl/lib/ line 0
BEGIN failed--compilation aborted.

An internal error occurred during: "Launching".java.lang.NullPointerException

i removed my Norton Anitvirus 2005, since the trialware has only one day
before it expires, after i uninstalled Norton Anitvirus 2005, the EPIC debugger
works, the Norton seems to hold the port 5000 so the dubugger can't connect
to it.

There is no reason that i have to uninstall Norton so that the EPIC debugger
can work, i prefer to perl -d, it is also very powerful.

The other problem is PadWalker, i download it from e-p-i-c and then install,
it does not work no doubt, so i download it from CPAN but it is a tarball,
i extract it in a Linux box but it is not a ppm, in order to install the
module, i need nmake.exe. Finally, i drop the EPIC debugger because i can't
sure the nmake.exe can work on Win2000 or not.

im waiting e-p-i-c for the PadWalker ppm which can work on ActivePerl v5.8.4.
aheid wrote on Wed Dec 15 16:07:18 CET 2004:
I had the same problem with the Debugger. My Debugger runs only when my
Norton Firewall ist disabled. 
Reg. the PadWalker Problem: I deinstalled the padwalker module i installed
over the Package Manager and installed the PadWalker Package from
and then it works for me. I have a similar Installation (WXP SP2/Activestate
Perl 5.8.4)

aheid wrote on Wed Dec 15 16:18:54 CET 2004:
Would be great, if someone has an idea what to do, to enable Debugging even
with firewall enabled. Perl.exe has been granted Access to connect to the
Internet. So this is not the problem.

luelljoc wrote on Fri Dec 17 10:29:52 CET 2004:

IMHO the whole thing works like this:

1. The Plugin tries to find an unused server port. After finding one (in
your case 5000) it opens the server socket.
2. The Perl debugger is started and tries to do a connect to the previously
opened socket (again 5000 in your case).

Step 2. seems not to work when Norton firewall is running. It might be that
the firewall considers the debugger connect as external connection attempt
and blocks it.
Maybe you should check your firewall ruleset (and the firewall logs, if

I don't have Norton firewall installed, so this is just a guess.

tkratz wrote on Sat Dec 18 11:01:45 CET 2004:
Same thing here with Outpost 2. The main problem is, that the plugin listens
on the first interface e.g. 192.168.x.x:5000 instead of  localhost:5000
or In the latter cases the firewall would remain silent.
This should be the default.

Could you test this? Should  I open an RFE?

pythonologist wrote on Tue Dec 28 04:01:18 CET 2004:
I am having problems on W2K all revolving around PadWalker. Put this simple
program in a file and run it from the command line as "perl":

use Data::Dumper ;
use PadWalker qw(peek_my);

sub display_caller {
    my $caller_hash = peek_my( 1 ) ;
    foreach my $key ( keys (%$caller_hash ) ) {    
	my $value = $caller_hash->{ $key } ;
	print $key, "=>", $value, "\n" ;
    print "\n" ;
    print "Contents: ", Dumper($caller_hash), "\n" ;

my $a="test1" ;
my $b ;
my @c = ( 1 , 2 ) ;
my $x=5;
my $y=3;
my $z=2;
display_caller( ) ;

it shows the hash of variables has garbage in them. Similar bad results
are shown if you run the program with the command line perl debugger "perl
-d" and step into the subroutine and then type "y 1" to display
callers environment. I've tried both and

Note: The above is an archived snapshot of a forum thread. Use the original thread at to post comments.