Run gdb /usr/bin/perl and at the gdb prompt "r myscript.pl" then enter. When it seg faults use the back trace command (bt) to see where it fell over and post it here. Someone might recognise the function it falls over in. It is quite possible the XML and postgres libraries both contain the same symbol for a function but take different arguments. When that function is called it will sometimes (depending on how everything is linked) only get resolved in one place so one of the calls will be wrong. You can get a list of symbols in the postgres and libxml libraries using nm if that is the case or when you get the back trace you can check for that symbol in each library to rule that in/out.

In reply to Re: Segmentation fault in DBI + XML::LibXML by mje
in thread Segmentation fault in DBI + XML::LibXML by furagu

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.