Re^2: EPIC Debugger not stopping at breakpoint

[wwe]

My debugger also fails with a message:

Use of uninitialized value in subroutine dereference at (null) line 1.
perl5db.pl did not return a true value.
BEGIN failed--compilation aborted.

Maybe i missed to install some modules. System is indows XP SP3 with Strawberry Perl 5.10 and EPIC 0.6.35 Update: after including perl/lib directory to project path like described on http://sourceforge.net/tracker/index.php?func=detail&aid=2907155&group_id=75859&atid=545274 the debugger works fine and stops on breakpoints.

...
Including the path to the perl5db.pl file (Perl\lib directory) to the 
+Perl
Include Path to my project (Project->Properties->Perl Include Path) wo
+rks
for me.

[adambe]

I finally got the debugger to stop at breakpoints:
1. Project -> Properties -> Perl Include Path
2. Make sure to add the following directory BEFORE c:\strawberry\perl\lib
c:\ECLIPSE_WORKSPACE\PROJECT_NAME\.metadata\.plugins\org.epic.debug

Change c:\ECLIPSE_WORKSPACE\PROJECT_NAME accordingly to match your configuration.

[Anonymous Monk]

Hi If anyone is checking for a more recent solution Why is the debugger not working (ActiveState or Strawberry Perl under Windows)? A recent release of PathTools (part of Perl distribution, file Cwd.pm) unfortunately contains a bug which breaks EPIC's debugger frontend. The specific symptom is the error message "perl5db.pl did not return a true value." - to see this message, you should enable the "debugger console" in EPIC Preferences. Furthermore, if you have this problem, debugging doesn't work at all. To fix it, you must edit Cwd.pm of your Perl distribution and remove the offending "eval" keyword from one line, as described in this bug report. DO NOT attempt to fix it by adding Perl's "lib" directory to your project's include path, as this will cause all breakpoints to be ignored!