My experience with debugging perl via EPIC has not been that positive. In general I have found that EPIC works well for simple scripts and demos, but if you attempt to debug something complex such a Catalyst application with it's very deep stack, or a DBIx::Class or Moose application with a complex and deeply inherited class structure, the whole thing grinds to a halt, and you frequently have to kill perl processes, and eclipse.
On the basis of that, my advice would be to learn how to use the perl command line debugger and debug over an SSH console session. If you must use a GUI debugger, then you could use the ptkdb debugger over an X11 session, but I don't recommend it.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||