Red Hat Bugzilla – Bug 433410
gdb: double free or corruption when restarting program after symbols changed
Last modified: 2008-05-13 11:26:07 EDT
Description of problem:
When restarting a program in gdb after making a change and recompiling, gdb
exits with *** glibc detected *** gdb: double free or corruption (!prev)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. run a program under gdb.. gdb some/program
2. close the program
3. make a change and recompile the program
4. restart the program
gdb exits with *** glibc detected *** gdb: double free or corruption (!prev)
gdb should not exit
Created attachment 295247 [details]
*** Bug 233276 has been marked as a duplicate of this bug. ***
It should be fixed in Rawhide/F9.
Upstream does not have this problem as it does not update / it has stale
information about the EXEC file being run which hurts support of PIEs
(Position-Independent-Executable) missing upstream.
The Fedora patch I put there for the EXEC file update was broken.
I grabbed 6.8-2 from koji. Appears to be fixed here. Tested on i386. Not tested
on x86_64, but I was seeing the problem on both. Thanks.
gdb-6.8-5.fc9 has been submitted as an update for Fedora 9
gdb-6.8-5.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report.