Hi Monks, Am a perl newbie working around an existing perl codebase which works with MySQL DB. My script execution is aborted with "*** stack smashing detected ***: perl terminated" error. I know it is hard to suggest a fix without the code. I am looking for ways to track to the source of the problem. Tried by commenting lines of code and push method on an array seem to be the source but the error log (below) confuses me.
*** stack smashing detected ***: perl terminated ======= Backtrace: ========= /lib/libc.so.6(__fortify_fail+0x4b)[0xb0a90b] /lib/libc.so.6(__fortify_fail+0x0)[0xb0a8c0] /usr/local/lib/perl/5.8.8/auto/DBD/mysql/mysql.so[0xfc75f4] /usr/local/lib/perl/5.8.8/auto/DBD/mysql/mysql.so(mysql_bind_ph+0x5ba) +[0xfb489a] /usr/local/lib/perl/5.8.8/auto/DBD/mysql/mysql.so(XS_DBD__mysql__st_bi +nd_param+0x1fe)[0xfc43de]
Any suggestions welcome

In reply to tracking "stack smashing detected" by manoj123

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.