I have downloaded a script that I hope will be useful to me, as it pertains to do something useful. But, it dies on me.

I want to submit a bug report to the author, and possibly a patch to fix the problem. But, I need to know more than just the line number, where it's failing. I've tried the Perl 5 debugger, and I suppose I could <tedious> single step my way into the previous line </tedious>, then use 'T' to get a traceback. The trouble is, that one the script has died, the stack is no longer there.

I have also looked at perl -MCarp=verbose as per the documentation on Carp, but this will only catch Carp generated exceptions, not normal die exceptions.

Is there an existing snippet, or a command line that will do the trick? Have I missed anything obvious?

Any help would be appreciated. My platform is Win32 by the way.

In reply to How do I get a post mortem stack trace? by rinceWind

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.