bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug ld/20537] New: Do not fail on overlapping FDEs in .eh_frame_hdr


From: raspy27 at gmail dot com
Subject: [Bug ld/20537] New: Do not fail on overlapping FDEs in .eh_frame_hdr
Date: Tue, 30 Aug 2016 14:07:18 +0000

https://sourceware.org/bugzilla/show_bug.cgi?id=20537

            Bug ID: 20537
           Summary: Do not fail on overlapping FDEs in .eh_frame_hdr
           Product: binutils
           Version: 2.27
            Status: UNCONFIRMED
          Severity: minor
          Priority: P2
         Component: ld
          Assignee: unassigned at sourceware dot org
          Reporter: raspy27 at gmail dot com
  Target Milestone: ---

Please provide possibility to not fail on .eh_frame_hdr overlapping issues
and/or provide --no-eh-frame-hdr option.

My use case: I have code which needs to link to some 3rd party libraries. When
linking with those libraries, final link ends with fatal error:

/usr/bin/ld: .eh_frame_hdr refers to overlapping FDEs.
/usr/bin/ld: final link failed: Bad value

I have read through [1] and I have also seen bug 17467. I understand that the
issue is originally caused by GCC and I have verified that new version of GCC
and binutils work smoothly when using ld -r. Trouble is that those 3rd party
libraries are compiled with an old toolchain that manifested bug 17467 and we
cannot recompile the library. 

I have verified that skipping --eh-frame-hdr makes linking succeed. However,
current GCC always automatically adds --eh-frame-hdr on linker call and there
is no --no-eh-frame-hdr option to override that. It would be good if such
option could be provided or the error could somehow be made a warning instead.
It seems that patch from [1] did not end up in the trunk, so the
-noinhibit-exec option does not seem to work around this issue.

[1] https://www.sourceware.org/ml/binutils/2014-09/msg00175.html

-- 
You are receiving this mail because:
You are on the CC list for the bug.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]