Red Hat Bugzilla – Bug 212780
/usr/bin/python: free(): invalid pointer: 0x08b84040
Last modified: 2007-11-30 17:11:46 EST
Description of problem:
*** glibc detected *** /usr/bin/python: free(): invalid pointer: 0x08b84040 ***
======= Backtrace: =========
BTW, "Abgebrochen" means "Canceled".
Version-Release number of selected component (if applicable):
Running system-config-date in TUI and quitting without any changes.
No invalid pointer... ;-)
BTW, same at system-config-keyboard in TUI. IMHO either newt/snack or python
Can you run with _MALLOC_CHECK_=2 and get a full backtrace from gdb?
Created attachment 139757 [details]
Is this what you expected to get by me?
I am providing the requested information for this bug *ticks*
this problem still happens in python-2.5-3.fc7.
Starting system-config-display, *** glibc detected *** python2: free(): invalid
pointer: 0x09c81b00 *** happens.
Created attachment 143485 [details]
another backtrace file
Ping? Nobody interested in fixing this annoying bug?
Sorry, thought I had reassigned to the right component after looking into it.
Hum? Why is this problem re-asssigned to pyxf86config? Any TUI application
(system-config-*) seems to be affected. IMHO the problem is somewhere between
newt and python, isn't it?
It appears that bug 220923 will be another instance, or closely related,
to this problem (although that appears to start quite a bit later
than a date on the original report from Robert Scheck).
Presumably glibc got stricter in catching those things as I see also
similar bombs which can be likely be traced back to bugs in fontconfig
or Tk (or both playing together?).
This is being caused by snack allocating memory with PyObject_Malloc and then
freeing it with PyMem_DEL. In python 2.5, these actually have a differences (so
that the interpreter can return memory to the system).
Fixed in newt-0.52.4-3.fc7
Yepp, your fix is confirmed to work in newt-0.52.4-3. Is there any reason why
you left open this bug report?
Forgot to hit the closed button :)