If you have no idea where in your code this error is being thrown, you can throw in some simple debug messages (not being able to see the code I have no idea how it's laid out)... if you put one every 1000 lines, you should easily be able to tell what chunk of code is causing the error, then narrow that down to 500, 200, 100, 50, etc. Then you'd have something you could post. Asking for help with code that you don't show is pointless.

In my opinion, simple print("debug 1"); print("debug 2"); etc. messages are highly underrated. When your script pukes, you can easily tell where, if it doesn't give you a meaningful error message.

/\ Sierpinski

In reply to Re^3: Perl58.dll & nt.dll crashes by sierpinski
in thread Perl58.dll & nt.dll crashes by ikkeniet

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.