About 15 years ago I helped someone debug a small program that remained silent while it should produce output. So we added a few debugging print statements. The program ran correctly (printing beside the debugging messages, also the messages it should). Removed the debugging, no messages at all. So we did a binary search to find out what the minimum amount of debugging messages printed was necessary.
A bare minimum. Printing an additional empty string made the program work correctly. No additional printing, and the program would not print at all.
Fast forward to a few months ago. I was trying to get an open source program working on an embedded system. It kept crashing with segmentation faults. Added debugging print statements - and it ran fine. Remove them, crash. Put them elsewhere, crash. Moved to a different place, and it ran fine. Eventually, I ended up with putting the following code in the program:
if(i == 0) abort();
This is after a for loop that left i to be equal to 256.
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.