Beefy Boxes and Bandwidth Generously Provided by pair Networks
Syntactic Confectionery Delight

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
The same goes for me.  The Perl debugger is one of those tools that I keep meaning to learn more about.

However, in my case I think it's because I have a background in C.  I've used several debuggers for compiled C code, but I always come back to using one of 2 things:  printf( ... ), and some mechanism of saving data to a logfile.

Part of my rationale in debugging that way in "C" is that it's best to take a "minimally invasive" approach when it comes to debugging.  If you have to recompile your program to support debugging, there's often a chance that you've changed the behavior of the bug; possibly even eradicated it.

One of the things I do at work is maintain the local Bugzilla code.  Whenever a tricky bug is found (as one was just this morning), the first thing I do is replicate the code and the mysql database to a test version on the same server (using a Perl script, of course ;-)), and then use some Perl subroutines to either print the data to the webpage, or save it to a logfile.  Once I've found and fixed the bug, I can migrate it back to the real version of the server fairly quickly.

So as I say, I'll learn about the debugger one of these days, I'm sure.  But when it comes to getting real work done, sometimes the old ways are the best.


In reply to Re: Using the Perl Debugger (-d) by liverpole
in thread Using the Perl Debugger (-d) by Melly

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • 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.
Log In?

What's my password?
Create A New User
Domain Nodelet?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others pondering the Monastery: (4)
As of 2024-06-19 03:24 GMT
Find Nodes?
    Voting Booth?

    No recent polls found

    erzuuli‥ 🛈The London Perl and Raku Workshop takes place on 26th Oct 2024. If your company depends on Perl, please consider sponsoring and/or attending.