The executeable is perl, you might have to supply the full path name, for example: /usr/bin/perl. Make sure it is exactly the same executable as caused the dump. If you are new to core dumps and gdb, one of the most useful short commands is bt, or "backtrace". This should give the routine it crashed in and the call stack. However you will only get that if perl have been compiled in debug (-g option to cc/gcc). Alos, if the call stack has been overwritten by the bug then you can't go much further.

Perl *shouldn't* crash, if it does then you have uncovered a bug which should be reported. Unless, that is, you are using some hokey module written in XS, have embedded C, or the like.

In reply to Re^3: Investigating segmentation core file in perl by cdarke
in thread Investigating segmentation core file in perl by Anonymous Monk

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.