In your petition you touch on one concern without recognising the more serious side of it. There is a design problem with your C function. It has a buffer overflow waiting to happen. Whether it's exploitable depends on the rest of your code, but a too-long error message may (depending on details of your system malloc() and cc ) cause segfaults, memory corruption, stack smashes, or trouble at work.

If the C function is declared as : int myfunction(char** errorstring);you can assign *errorstring within the function after mallocing to fit and copying your string to the new buffer.

I regret that I don't yet know enough xs and perlguts to advise you on what C constructions are most convenient for perl.

After Compline,
Zaxo

In reply to Re: Passing a string from C to Perl by Zaxo
in thread Passing a string from C to Perl 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.