Created attachment 431479 [details]
Old Backtrace, New Backtrace and Binary to reproduce
Description of problem:
gdb produces invalid backtraces.
for example stackframe of threads:
#12 0x0000000001db3818 in ?? ()
#13 0x00000000477c3c01 in ?? ()
#14 0x00000000477c3c50 in ?? ()
Cannot access memory at address 0x2f1b16068d234f5
Version-Release number of selected component (if applicable):
7.0.1-23.el5 (gdb-6.8-37.el5 - RHEL 5.4 - works perfectly)
Steps to Reproduce:
1. Call Binary "BinaryToReproduce"
2. Binary will crash automatically with signal 6
3. Analyze coredump with gdb - following steps:
3.2 info threads
3.3 thread apply all backtrace
see gdb.BinaryToReproduce_7.0.1-23.el5.txt in attached zip-archive.
see gdb.BinaryToReproduce_gdb-6.8-37.el5.txt in attached zip-archive.
Binary compliled with gcc version 4.1.2 20080704 (Red Hat 4.1.2-48).
Fix + testcase at:
This is a regression against RHEL-5.4.
Thanks for quickly fixing this problem.
We will verifiy it as soon as the fixed redhat rpm will be available.
Which rpm version will include the bugfix?
Please open Issue Tracker with GSS (support services) for a possible RHEL rpm access. Binary rpm will be available only with RHEL-5.6 in the future otherwise.
The upstream posted patch applies cleanly to the RHEL-5.5 src.rpm sources.
It will be binary built for Fedora today - but that is Bug 614604.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
GDB could have failed to backtrace some functions of binary files. This occurred when some of the source files of a single binary file were compiled with debug information (gcc -g), and some without it. With this update, GDB finds all Call Frame Information (CFI) present in the binary file and backtraces correctly.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.