This thread reminded me of an old node about debugging and the use of debuggers. And I can only dream of a shred of the skills of some monks in that thread.

About your problem: perhaps it has little to do with your code or the library you are working with. Are you interested in the system you find the segfault with, i.e. is it important to you? Perhaps it is a heavily patched, manual installation as opposed to a freshly installed popular distribution. Perhaps you cannot even repeat the segfault with the same distribution on slightly different hardware.

Hope this helps,
Jeroen

"We are not alone"(FZ)

In reply to Re: GDB journey into perl internals by jeroenes
in thread GDB journey into perl internals by cosimo

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.