You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2004/09/02 00:49:36 UTC

[Bug 3742] New: previous fix for umask causes potential untie() issues

http://bugzilla.spamassassin.org/show_bug.cgi?id=3742

           Summary: previous fix for umask causes potential untie() issues
           Product: Spamassassin
           Version: SVN Trunk (Latest Devel Version)
          Platform: Other
        OS/Version: other
            Status: NEW
          Severity: blocker
          Priority: P1
         Component: Libraries
        AssignedTo: dev@spamassassin.apache.org
        ReportedBy: felicity@kluge.net


Apparently the fix from bug 3731 causes DBM to be unable to untie() on certain platforms (at least 
Windows, possibly all,) because we do:

$res = tie ...

so that $res gets a copy of the tie object, and apparently untie() doesn't deal well with both the array 
and the object hanging around, netting:

            carp "untie attempted while $count inner references still exist" if $count;

according to the perltie doc:

       To get the script to work properly and silence the warning make sure
       there are no valid references to the tied object before untie() is
       called:

           undef $x;
           untie $fred;

patch due shortly.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.