Jarkko Hietaniemi wrote: >> refcnt_dec: fd 3: 0 <= 0 > > Sigh... the perlio refcnt saga just keeps going on. Well, all I can > say about that croak is that it tries to guard against someone trying > to decrement the refcnt of a perlio stream when the refcnt is already > down to zero (or even less...) If you are doing some sort of shared > streams you could maybe increment the perlio refcnt? No shared streams here, I'm afraid. The shared file open business just lets you control whether or not other processes can also read and/or write a file that you've just opened. Sort of like flock(), only mandatory rather than advisory. And in my reply to Yves I showed exactly the same problem crops up with plain old fopen() too. So presumably something is wrong somewhere in PerlIO-land that causes the refcnt to be decremented too far, and this new croak() is simply revealing a bug that has probably been there since the year dot? -- ------------------------------------------------ Radan Computational Ltd. The information contained in this message and any files transmitted with it are confidential and intended for the addressee(s) only. If you have received this message in error or there are any problems, please notify the sender immediately. The unauthorized use, disclosure, copying or alteration of this message is strictly forbidden. Note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Radan Computational Ltd. The recipient(s) of this message should check it and any attached files for viruses: Radan Computational will accept no liability for any damage caused by any virus transmitted by this email.Thread Previous | Thread Next