Since using a debugger tends to elongate the time between the execution of lines in code (because the user needs to manually move the program ahead), data has more time to be processed and buffered, therefore not crashing.

At any rate, I assume you mean http://zim-wiki.org which is a fine thing to be called a script, and has its own, very detailed installation page(s). Along with an FAQ, manual, Bug-Tracker etc.

On the other hand, you might be referring to something else, which in that case, I hope another monk will be more handy with a guess of what you want

Stop saying 'script'. Stop saying 'line-noise'.
We have nothing to lose but our metaphors.

In reply to Re: Segfaults but ok in debugger by Erez
in thread Segfaults but ok in debugger by m.e

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


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.