Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#652 Breakpoints don't trigger reliably in 5.16

open
Stephan Ruehl
Debugger (177)
5
2014-03-25
2012-11-20
Aaron Priven
No

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.

Discussion

  • Aaron Priven
    Aaron Priven
    2012-11-20

    If I replace perl5db.pl version 1.37 which comes with perl 5.16.1 with version 1.34 which comes with perl 5.14.2, then it works. So it must be some incompatibility with perl5db.pl 1.37. I'm not sure what the incompatible change was, though.

     
  • Aaron Priven
    Aaron Priven
    2014-03-25

    Well, in the "Better Late Than Never" department, it appears that the working version of perl5db.pl is actually 1.33, not 1.34. (This is after upgrading to Mavericks and Kepler.) There are a number of changes to breakpoint handling in 1.34 but I don't really understand the code (sorry!)