Hi Guys,
I'm using using the wonderful open3 calling routine promoted by ikegami, Re: Catching errors (II).
We are regression testing at the moment and I'm still getting sporadic segfaults which are not always easily repeatable.
Is it possible to find the perl line number, with backtrace, if possible, of where the error occurred? Perl must have had this up to the pont of the crash, so I wondered if I could to retrieve it in my error reporting.
Otherwise, maybe I should run Devel::Trace, or something similiar, while testing.
What do you think?
Thanks in advance,
Regards
Steve.
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.