Re^2: Eclipse / EPIC / Win32, Debugger Problems / perl5db.pl did not return a true value, Perl 5.10.1

Thanks for your reply. I reinstalled the PadWalker PPD, but the problem remains the same. I also tried the following PPDs, with no effort yet:

http://ppm4.activestate.com/MSWin32-x86/5.10/1006/R/RO/ROBIN/PadWalker
+-1.7.ppd
http://ppm4.activestate.com/MSWin32-x86/5.10/1006/R/RO/ROBIN/PadWalker
+-1.9.ppd (this one should have fixed the problem)
http://www.bribes.org/perl/ppm/PadWalker.ppd
[download]

Regards, vifo

Comment on Re^2: Eclipse / EPIC / Win32, Debugger Problems / perl5db.pl did not return a true value, Perl 5.10.1 Download Code

Replies are listed 'Best First'.
Re^3: Eclipse / EPIC / Win32, Debugger Problems / perl5db.pl did not return a true value, Perl 5.10.1 by Garen (Initiate) on Sep 10, 2010 at 20:23 UTC
Perl 5.10.1 introduced a one-line change in Cwd.pm that broke debugging on Windows which may be the same issue you're having, see: https://rt.cpan.org/Public/Bug/Display.html?id=56225	[reply]
Re^3: Eclipse / EPIC / Win32, Debugger Problems / perl5db.pl did not return a true value, Perl 5.10.1 by Anonymous Monk on Feb 01, 2010 at 16:24 UTC
You should file a bug report ;)	[reply]
Re^4: Eclipse / EPIC / Win32, Debugger Problems / perl5db.pl did not return a true value, Perl 5.10.1 by Anonymous Monk on Mar 21, 2010 at 17:35 UTC
I had the same problem after upgrading to ActivePerl 5.10.1.1007 for windows. I then cleaned and did a fresh install of 1007, and still had the same problem. I recleaned. and installed ActivePerl 5.10.1.1006 and everything was fine. I hope this helps. Nigel	[reply]
Re^5: Eclipse / EPIC / Win32, Debugger Problems / perl5db.pl did not return a true value, Perl 5.10.1 by dvwilbur (Initiate) on Mar 30, 2010 at 19:25 UTC
Great help! I also had this problem and backed up to build 1006 (glad I still had the install binary in my downloads area) and EPIC debugging works again! Thanks.	[reply]
Re^5: Eclipse / EPIC / Win32, Debugger Problems / perl5db.pl did not return a true value, Perl 5.10.1 by Anonymous Monk on Jun 25, 2010 at 02:13 UTC
thanks for your advise. This problem have made me want to cry. N I can debug my perl program. I have changed the ActivePerl 5.10.1.1200 to ActivePerl 5.10.1.1006.	[reply]