Bug 588678 - gcc emits incorrect unwind info on i?86/x86_64
Summary: gcc emits incorrect unwind info on i?86/x86_64
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gcc
Version: 13
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Keywords:
Depends On:
Blocks: F13Target
TreeView+ depends on / blocked
 
Reported: 2010-05-04 09:25 UTC by Jakub Jelinek
Modified: 2010-05-05 07:23 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2010-05-05 07:23:58 UTC


Attachments (Terms of Use)

Description Jakub Jelinek 2010-05-04 09:25:33 UTC
As mentioned in:
http://lists.dwarfstd.org/private.cgi/dwarf-discuss-dwarfstd.org/2010-April/000847.html
http://gcc.gnu.org/ml/gcc-patches/2010-04/msg01422.html
and following threads, GCC generates invalid unwind info on i?86/x86_64, where DW_OP_cfa_def_cfa_expression is followed by DW_OP_cfa_def_cfa_{register,offset{,_sf}} and thus either the CFA offset or register is undefined.  It is not possible to unwind through such code then.

Comment 1 Fedora Update System 2010-05-04 09:30:25 UTC
gcc-4.4.4-2.fc13,libtool-2.2.6-20.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/gcc-4.4.4-2.fc13,libtool-2.2.6-20.fc13

Comment 2 Fedora Update System 2010-05-04 23:52:21 UTC
gcc-4.4.4-2.fc13, libtool-2.2.6-20.fc13 has been pushed to the Fedora 13 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update gcc libtool'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/gcc-4.4.4-2.fc13,libtool-2.2.6-20.fc13

Comment 3 Fedora Update System 2010-05-05 07:23:50 UTC
gcc-4.4.4-2.fc13, libtool-2.2.6-20.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.