This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/15407] Partial frame info in sysdeps/x86_64/start.S
- From: "hjl.tools at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Mon, 29 Apr 2013 16:11:31 +0000
- Subject: [Bug libc/15407] Partial frame info in sysdeps/x86_64/start.S
- Auto-submitted: auto-generated
- References: <bug-15407-131 at http dot sourceware dot org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=15407
--- Comment #11 from H.J. Lu <hjl.tools at gmail dot com> 2013-04-29 16:11:31 UTC ---
We have
[hjl@gnu-6 start-2]$ g++ foo.o -v
...
/usr/libexec/gcc/x86_64-redhat-linux/4.7.2/collect2 --build-id --no-add-needed
--eh-frame-hdr --hash-style=gnu -m elf_x86_64 -dynamic-linker
/lib64/ld-linux-x86-64.so.2
/usr/lib/gcc/x86_64-redhat-linux/4.7.2/../../../../lib64/crt1.o
/usr/lib/gcc/x86_64-redhat-linux/4.7.2/../../../../lib64/crti.o
/usr/lib/gcc/x86_64-redhat-linux/4.7.2/crtbegin.o
-L/usr/lib/gcc/x86_64-redhat-linux/4.7.2
-L/usr/lib/gcc/x86_64-redhat-linux/4.7.2/../../../../lib64 -L/lib/../lib64
-L/usr/lib/../lib64 -L/usr/lib/gcc/x86_64-redhat-linux/4.7.2/../../.. foo.o
-lstdc++ -lm -lgcc_s -lgcc -lc -lgcc_s -lgcc
/usr/lib/gcc/x86_64-redhat-linux/4.7.2/crtend.o
/usr/lib/gcc/x86_64-redhat-linux/4.7.2/../../../../lib64/crtn.o
[hjl@gnu-6 start-2]$
All EH frame info should be between crtbegin[ST].o and crtend.o. When
EH frame is added in crt1.o, it is placed before crtbegin.o. It isn't a
problem for crtbegin[S].o since it doesn't define __EH_FRAME_BEGIN__
and bfd linker effectively ignores EH frame in crt1.o. When gold sees EH
frame before crtbeginT.o, which is used to mark the start of EH frame with
__EH_FRAME_BEGIN__, it places .eh_frame section in crtbeginT.o to the end
of output .eh_frame section. It is quite odd to place any EH frame info
before __EH_FRAME_BEGIN__.
--
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.