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.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
