Re^3: EPIC Debugger not stopping at breakpoint

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.

Comment on Re^3: EPIC Debugger not stopping at breakpoint

Replies are listed 'Best First'.
Re^4: EPIC Debugger not stopping at breakpoint by petro4213 (Acolyte) on Jul 15, 2024 at 08:23 UTC
It is 2024 now and this problem and the solution is still the same: You have to manually add c:\ECLIPSE_WORKSPACE\PROJECT_NAME\.metadata\.plugins\org.epic.debug as you described - and there's no way to order the individual include paths afterwards - you have to add them in the order you want them to appear... Anyway for me, it doesn't break on breakpoints set in any package file - it only breaks at breakpoints set in the main file. Moreover, if I set a breakpoint in a package file and another one in the main file, the debugger stops at the latter each time the breakpoint in the package file is hit - very strange.	[reply]
Re^4: EPIC Debugger not stopping at breakpoint by Anonymous Monk on Feb 12, 2015 at 12:22 UTC
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!	[reply]