Bug 1048581

Summary: python lzma binding segfault when __init__ with non-existent file after executing the constructor (Python 2.7)
Product: [Fedora] Fedora Reporter: sky.kok
Component: pyliblzmaAssignee: François Cami <contribs>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 18CC: contribs
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 22:37:24 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description sky.kok 2014-01-05 14:03:28 UTC
Description of problem:

python lzma binding segfault when __init__ with non-existent file after executing the constructor (Python 2.7)

Version-Release number of selected component (if applicable):

pyliblzma-0.5.3-7.fc18.x86_64 

How reproducible:

Always.

Steps to Reproduce:
1. [sky@localhost cutecat]$ cat /tmp/lzma_segfault.py 
import lzma
file = lzma.LZMAFile("/tmp/file.lzma", "w")
file.write(b"xxxx")
file.close()
with lzma.LZMAFile("/tmp/file.lzma", "w") as f:
    f.__init__("non-existent")
2. [sky@localhost cutecat]$ python /tmp/lzma_segfault.py 

Actual results:

Segmentation fault (core dumped)

Expected results:

Not crash.

Additional info:

See also http://bugs.python.org/issue19878

The official python 2.7 does not provide lzma binding. See http://bugs.python.org/issue19885.

Comment 1 Fedora End Of Life 2014-02-05 22:37:24 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.