I have not used IPC::ShareLite, and am at home without a Unix machine to test, but after looking through the module, it appears the invalid arg message is caused by a return of undef from read_shre (the XS function).

as i said, i have not tested this, but here is what i am seeing :
1. fetch (SharLite.pm) calls read_share
2. read_share (ShareLite.xs) calls system function, and return string, or undef if string length is <= 0
3. fetch (ShareLite.pm) error if return from read_share is undef

Based on this, i would guess that if fetch() is being called prior to adding data to the share, it could possibly error ... but, thats just a guess.

may the foo be with you

In reply to Re: Problems with IPC::ShareLite by MZSanford
in thread Problems with IPC::ShareLite by raxor

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.