Bug 243762

Summary: glibc issue invalid pointer on free()
Product: [Fedora] Fedora Reporter: Jochen Schmitt <jochen>
Component: PyQtAssignee: Than Ngo <than>
Status: CLOSED NOTABUG QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: 7CC: katzj
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-06-12 15:58:35 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Backtrace of the python issue none

Description Jochen Schmitt 2007-06-11 18:58:53 UTC 
Description of problem:


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


How reproducible:
Start luma
open browser
click on plus button of the server

  
Actual results:
*** glibc detected *** python: free(): invalid pointer: 0x00002aaaaab1b418 ***

Programm hangs

Expected results:
Normal working

Additional info:
This issue occured von python-2.5.1 (cvsI too.

Orignal bug is #221167
Comment 1 Jeremy Katz 2007-06-11 19:14:22 UTC 
This is almost certainly not a python bug and instead a bug in one of the
bindings used by luma.  Python2.5 changes things so that you must consistently
use either PyObject or PyMem allocation rather than mixing and matching between
the two.  

Would need a backtrace with -debuginfos installed to get a better idea of which
is the causer.  Or a good way to set up luma to use it.
Comment 2 Jochen Schmitt 2007-06-11 19:21:07 UTC 
Created attachment 156750 [details]
Backtrace of the python issue
Comment 3 Jeremy Katz 2007-06-11 19:42:15 UTC 
Okay, that's coming from PyQT (or what's generated by sip)
Comment 4 Jochen Schmitt 2007-06-12 15:58:35 UTC 
I have found out, that the issue was raise by python-ldap. After a update to
python-ldap-2.3 the issue doesn't occure anymore.