Could you tell me why the address is invalid.

Aye, there's the rub. Usually a duff pointer, all you have to do is find which one (that's a joke, by the way). Thing is that all you are seeing is the result of a memory location being overwritten, not the cause. A needle in a haystack is simple to these kinds of issues. Just because it was failing in the Sybase module does not mean that that module caused the fault - just that it happened to be the area of memory stomped on.

You will not stand much chance using gdb unless you recompile perl and any XS modules with debug switched on (unless you are really good at assembler), and that is not for the faint hearted. Realistically you must try to reproduce the fault and then remove code until it stops happening. Personally I have known bugs like this to have a life of five or six years and never get resolved. Part of the joys of C.

By the way, are you using a reasonably up-to-date version of Perl and associated modules? It might be worth considering an upgrade if you are not.

In reply to Re^3: Understanding the segmentation fault output generated using gdb by cdarke
in thread Understanding the segmentation fault output generated using gdb 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.