Howdy,
As a follow up to the perl debugging session from last month, I wanted
to let everyone know that the latest and greatest from EPIC now sees
the breakpoints correctly. If you were there, you'll remember that
setting breakpoints in modules didn't seem to work--the breakpoint
only was recognized when it was in the main file. You can now set
breakpoints in other files using the editor, and when they get
executed by your debugging process, the breakpoint is properly
recognized.
I believe the issue came down to how the EPIC debugger interface
exported the break points to the perl debugger. It's my understanding
(from reading the bugs at SF) that the EPIC debugger wasn't specifying
the filename + breakpoint correctly. The method used worked fine on
the main file, but when you were in an included module, the breakpoint
failed to match up. The latest EPIC testing release 0.6.35 works great!
I'm actually planning on using the debugger for a code review at my
current client. I figure we can fire up our web app, set some break
points, and then follow the code execution. When we hit a specific
section we want to review, we step through it and discuss what is
going on.
Matt
--
Matt Luker
*/rsh tech
your source for programming know-how
phone: 617.418.3480
email: [email protected]
web: http://www.rshtech.com/
_______________________________________________
Boston-pm mailing list
[email protected]
http://mail.pm.org/mailman/listinfo/boston-pm
