I'm not a GDB expert either, and I have only a general knowledge of the perl internals, so what I do to catch these errors is to run the code through valgrind with increasing levels of verbosity until I get to the point where the errors start to make sense. (As usual, it really helps here if your code is split up in fairly small functions)

I usually don't go stepping through the code, since that takes a long time and is generally boring. I just throw in a lot of assert()s and log/warn marcros in my XS code on the suspicious parts. That way I can just compile with NDEBUG or not depending on if I'm developing or compiling production code.

"What should it profit a man, if he should win a flame war, yet lose his cool?"

In reply to Re: GDB journey into perl internals by Joost
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.