[Bug binutils/14416] .eh_frame section not copied correctly by --only-keep-debug
http://sourceware.org/bugzilla/show_bug.cgi?id=14416 Alan Modra changed: What|Removed |Added Status|NEW |RESOLVED CC||amodra at gmail dot com Resolution||INVALID --- Comment #4 from Alan Modra 2012-07-29 23:49:34 UTC --- Not a bug -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. ___ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
[Bug binutils/14416] .eh_frame section not copied correctly by --only-keep-debug
http://sourceware.org/bugzilla/show_bug.cgi?id=14416 --- Comment #3 from Andreas Schwab 2012-07-29 13:10:21 UTC --- .eh_frame is handled like all other non-debug sections. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. ___ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
[Bug binutils/14416] .eh_frame section not copied correctly by --only-keep-debug
http://sourceware.org/bugzilla/show_bug.cgi?id=14416 --- Comment #2 from Rene Gollent 2012-07-29 12:01:31 UTC --- (In reply to comment #1) > .eh_frame is not a debug section. It is a loaded section so it will never be > stripped from the original object. 1) Then why does it appear in the resulting .debug file at all? and 2) This still leaves the problem that on e.g. gcc 4.6.2, -g only outputs .eh_frame. I've looked through the bug database and this appears to be deliberate since the contents carry so much overlap with .debug_frame. Therefore, if .debug_frame isn't going to be output, then .eh_frame needs to be correctly copied, else there is no way for the debugger to unwind the call frame. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. ___ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
[Bug binutils/14416] .eh_frame section not copied correctly by --only-keep-debug
http://sourceware.org/bugzilla/show_bug.cgi?id=14416 --- Comment #1 from Andreas Schwab 2012-07-29 11:56:31 UTC --- .eh_frame is not a debug section. It is a loaded section so it will never be stripped from the original object. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. ___ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
[Bug binutils/14416] New: .eh_frame section not copied correctly by --only-keep-debug
http://sourceware.org/bugzilla/show_bug.cgi?id=14416 Bug #: 14416 Summary: .eh_frame section not copied correctly by --only-keep-debug Product: binutils Version: 2.22 Status: NEW Severity: normal Priority: P2 Component: binutils AssignedTo: unassig...@sourceware.org ReportedBy: r...@gollent.com Classification: Unclassified When using objcopy --only-keep-debug to generate a separate symbolic debugging information file (as specified at http://sourceware.org/gdb/onlinedocs/gdb/Separate-Debug-Files.html ), .eh_frame doesn't appear to be copied correctly. The section is present and is the same size as that of the originating file, but doesn't contain valid CIE/FDEs, instead showing only: Contents of the .eh_frame section: ZERO terminator 0004 ZERO terminator 0008 ZERO terminator [...etc.] This problem doesn't seem to be exhibited for .debug_frame though. However, since some newer versions of gcc only output .eh_frame by default, this can be a bit troublesome for debugging. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. ___ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
