I don't know. The information is surely available somewhere (since the program needs to resume after the handler exits), but it might not be easy to obtain.

You could trace the code using a debugger. Tracing displays each executed line as it is executed.

Alternatively, you could do some manual tracing. Put a few print statements in strategic locations — don't forget to turn off buffering — and run the program. Now that you have a better idea where the problem is, put more print statements in that area and run the program again. Repeat this process until you locate the problem. This is the same idea behind binary searches.

In reply to Re: determining the line# of code when an alarm() trips? by ikegami
in thread determining the line# of code when an alarm() trips? by ManFromNeptune

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.