comment on

On a couple of occasions I have been debugging some script which uses an external datafile for input. I had the script and the datafile up in the editor, laboriously following the execution path, adding print here and there and nothing makes sense. You get the picture.

Hey, even basic stuff don't come out as expected. Only Hubris refrained me seeking help as I sensed something was "rotten in Denmark".

Only after too much time was spent I realized the the datafile I was viewing and the script was reading was not the same. In fact there was never anything wrong with the script in the first place!!

So I guess the morale of the story is that a "bug" can be caused by the script, data or yourself, more seldom in my experience by hardware or the OS.

---
[download]

Error, mistake, slip, blunder, lapse? I prefer to think of it as an 'unfortunate juxtaposition of circumstances'.

In reply to Re: Looking For The Obvious - Debugging Perl by guha
in thread Looking For The Obvious - Debugging Perl by greenFox

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.


XP is just a number
	PerlMonks