--
What|Removed |Added
CC||mkl at pengutronix dot de
http://sourceware.org/bugzilla/show_bug.cgi?id=3206
--- You are receiving this
--- Additional Comments From MatthewLCreech at eaton dot com 2006-09-15
13:55 ---
Okay, I got around to building a binutils snapshot (9/13), and I now get the
behavior described by Kevin Hilman:
LD .tmp_vmlinux1
arm-linux-gnueabi-ld: .tmp_vmlinux1: sh_link of section
`.ARM.exidx.
--- Additional Comments From hjl at lucon dot org 2006-09-14 22:19 ---
Please check out binutils in CVS. If you can provide a testcase with assembly
files so that I can produce it with binutils only, I will take a look.
--
What|Removed |Added
-
--- Additional Comments From MatthewLCreech at eaton dot com 2006-09-14
21:10 ---
Interestingly, though, if I change this portion to:
*(.exit.text)
*(.ARM.exidx)
*(.ARM.extab)
*(.exit.data)
*(.exitcall.exit)
it no longer segfaults for this test case. This isn't a proper fix, though, a
--- Additional Comments From MatthewLCreech at eaton dot com 2006-09-14
20:09 ---
I tried both:
*(.exit.text)
*(.ARM.exidx.exit.text)
*(.exit.data)
*(.exitcall.exit)
as well as
*(.ARM.exidx.exit.text)
*(.exit.data)
*(.exitcall.exit)
and both still trigger a segfault.
--
http://so
--- Additional Comments From hjl at lucon dot org 2006-09-14 19:05 ---
It is because -fasynchronous-unwind-tables adds .ARM.exidx sections.
Please try to change kernel linker script from
/DISCARD/ : { /* Exit code and data */
*(.exit.t
--- Additional Comments From MatthewLCreech at eaton dot com 2006-09-14
18:30 ---
Additional info. provided by Kevin Kilman at MontaVista:
[Quote]
FYI... I've seen the same thing using a MontaVista gcc 4.1.2, ld 2.17.
However, after a binutils update to 2.17.50 20060808, it no longer
se
--- Additional Comments From MatthewLCreech at eaton dot com 2006-09-14
17:49 ---
Created an attachment (id=1296)
--> (http://sourceware.org/bugzilla/attachment.cgi?id=1296&action=view)
Tarball of test files
1. Install arm[-none]-linux-gnueabi toolchain
2. Extract tarball contents
3. S
