I am running Eclipse Juno on Mac OS X Mountain Lion. I use ActiveState Perl for Mac.
When I try to debug a program in perl 5.16,1 it steps properly, but it does not trigger breakpoints reliably. It appears to depend where it is in the program -- it will trigger a breakpoint if I hit the green run icon if the breakpoint is in the same area, but not in subroutines further down.
If I instead use 5.14.2 to debug the same program, breakpoints trigger properly.
I don't really understand how the debugger works, either on its own or in EPIC, but I notice that 5.16 made changes to the debugger, according to the perl5160delta document. Notably, it says "New option for the debugger's t command: The t command in the debugger, which toggles tracing mode, now accepts a numeric argument that determines how many levels of subroutine calls to trace." I don't know if this is what's affecting EPIC, but it seems like it might be related.