I'm afraid the 'best way' to debug anything depends on what you are debugging, what the exact problem is you are debugging, and your debugging preferences. So I'm afraid I can't give you the 'best way'.
I sometimes use a debug switch in my code at critical points like:
my $DEBUG=1;
...
my $val = get_something("vars");
warn $val if ($DEBUG && ! $val);
...
my $val2 = do_something_else($val);
warn $val2 if ($DEBUG && $val2 =~ /^\w{2}\d{2}$/);
This way you can turn off/on debugging by (un)setting the master-switch $DEBUG, and even use different $DEBUG values for different types of debugging, the sky is the limit.
If you want to see the call tree of your program you could use Devel::Dprof.
If you want to see the content of complex structures, you could use Data::Dumper.
Some people really like the perl debugger, you can do some cool tricks with it, see the perldebug docs.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
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:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.