Bug 782438

Summary: rpm-python heap corruption
Product: [Fedora] Fedora Reporter: Pádraig Brady <p>
Component: rpmAssignee: Panu Matilainen <pmatilai>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: ffesti, jnovy, pmatilai
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-05-11 06:44:08 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Pádraig Brady 2012-01-17 13:49:41 UTC 
With fully updated 64 bit Fedora 16 host and guest, I got this in the guest:

yum -y install wordpress httpd ' failed(255):
*** glibc detected *** /usr/bin/python: free(): invalid next size (fast): 0x00000000056b1340 ***
======= Backtrace: =========
/lib64/libc.so.6(+0x7c2d6)[0x7fe341b0d2d6]
/lib64/libc.so.6(+0x7d5be)[0x7fe341b0e5be]
/usr/lib64/librpmio.so.2(rfree+0x9)[0x7fe33a636139]
/usr/lib64/librpm.so.2(+0x29e1d)[0x7fe33b21ee1d]
/usr/lib64/librpm.so.2(+0x2a55c)[0x7fe33b21f55c]
/usr/lib64/librpm.so.2(+0x2918c)[0x7fe33b21e18c]
/usr/lib64/librpm.so.2(fsmSetup+0x26c)[0x7fe33b220b9c]
/usr/lib64/librpm.so.2(+0x2f934)[0x7fe33b224934]
/usr/lib64/librpm.so.2(+0x3084c)[0x7fe33b22584c]
/usr/lib64/librpm.so.2(+0x3f9fa)[0x7fe33b2349fa]
/usr/lib64/librpm.so.2(rpmtsRun+0x9e5)[0x7fe33b23b145]
/usr/lib64/python2.7/site-packages/rpm/_rpmmodule.so(+0xedce)[0x7fe33b465dce]
/usr/lib64/libpython2.7.so.1.0(PyObject_Call+0x53)[0x7fe342737193]
/usr/lib64/libpython2.7.so.1.0(PyEval_CallObjectWithKeywords+0x47)[0x7fe3427c8457]
/usr/lib64/libpython2.7.so.1.0(+0x5de0c)[0x7fe34274be0c]
/usr/lib64/libpython2.7.so.1.0(PyObject_Call+0x53)[0x7fe342737193]
/usr/lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x3d55)[0x7fe3427cc795]
/usr/lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x5b40)[0x7fe3427ce580]
/usr/lib64/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x855)[0x7fe3427cf5a5]
/usr/lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x509b)[0x7fe3427cdadb]
/usr/lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x5b40)[0x7fe3427ce580]
/usr/lib64/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x855)[0x7fe3427cf5a5]
/usr/lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x509b)[0x7fe3427cdadb]
/usr/lib64/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x855)[0x7fe3427cf5a5]
/usr/lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x509b)[0x7fe3427cdadb]
/usr/lib64/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x855)[0x7fe3427cf5a5]
/usr/lib64/libpython2.7.so.1.0(PyEval_EvalCode+0x32)[0x7fe3427cf6d2]
/usr/lib64/libpython2.7.so.1.0(+0xfb9ec)[0x7fe3427e99ec]
/usr/lib64/libpython2.7.so.1.0(PyRun_FileExFlags+0x90)[0x7fe3427ea7f0]
/usr/lib64/libpython2.7.so.1.0(PyRun_SimpleFileExFlags+0xdf)[0x7fe3427eb26f]
/usr/lib64/libpython2.7.so.1.0(Py_Main+0xb85)[0x7fe3427fc745]
/lib64/libc.so.6(__libc_start_main+0xed)[0x7fe341ab269d]
/usr/bin/python[0x400651]
Comment 1 Pádraig Brady 2012-01-17 14:14:23 UTC 
Just tried everything again in a new VM using the exact same steps and it's not reproducible.  I'll do a mem test on the machine later. I wonder might it be related to bug #607650
Comment 2 Panu Matilainen 2012-05-11 06:44:08 UTC 
Yup, problems that only occur on VM (and are not reproducable even there) are unlikely to be rpm bugs but kernel issues, wouldn't be the first and unlikely to be the last time either.

Closing NOTABUG (sure was a bug involved but probably not in rpm)