develooper Front page | perl.perl5.porters | Postings from November 2006

Re: Trouble with PERLIO_INIT/PERLIO_TERM changes

Thread Previous | Thread Next
From:
Steve Hay
Date:
November 29, 2006 10:11
Subject:
Re: Trouble with PERLIO_INIT/PERLIO_TERM changes
Message ID:
456DCCB9.5080304@uk.radan.com
Jarkko Hietaniemi wrote:
>> 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?
> 
> Possibly.  Something is causing the refcnt to become out of sync.
> Have you tried setting $ENV{PERLIO_DEBUG} to point to a file?
> (The file will be overwritten with PerlIO's internal mumblings.)

Attached is the output of running "perl -Mblib test.pl" in my Foo module 
with PERLIO_DEBUG pointing to a file.

This time the test program dies with "refcnt_dec: fd 4: 0 <= 0" 
(presumably debug.txt itself is now fd 3).

I'm not sure that it helps me very much.

I'm leaving now, but I'll have a closer look tomorrow (unless you've 
sorted it all out by then ;-)

-- 


------------------------------------------------
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


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About