I am using ld from binutils 2.15. It bombs on multiple solaris 8
systems, always while accessing /usr/lib/libm.so (I know this from
truss). When I compile, I see one of these:
collect2: ld terminated with signal 10 [Bus Error]
collect2: ld terminated with signal 11 [Segmentation Fault]
When running truss on 1 system, I get:
6857: read(9, "\0\0\0\0\0\0\0\0\0\0\0\0".., 8192) = 8192
6857: Incurred fault #5, FLTACCESS %pc = 0x0005DCCC
6857: siginfo: SIGBUS BUS_ADRALN addr=0x1200001A
6857: Received signal #10, SIGBUS [default]
6857: siginfo: SIGBUS BUS_ADRALN addr=0x1200001A
and on another I get
13980: read(10, "\0\0\0\0\0\0\0\0\0\0\0\0".., 8192) = 8192
13980: brk(0x008A2478) = 0
13980: brk(0x008A4478) = 0
13980: Incurred fault #6, FLTBOUNDS %pc = 0x0005DB4C
13980: siginfo: SIGSEGV SEGV_MAPERR addr=0x00000018
13980: Received signal #11, SIGSEGV [default]
13980: siginfo: SIGSEGV SEGV_MAPERR addr=0x00000018
In both cases, they occur while reading libm.so (and the same number
of read() calls at that.) I tried installing the latest libm.so from
Sun, but it didn't help. If I use the solaris ld, all is fine.
Anyone have any ideas how to correct this?
Thanks,
Bob
|
|
0
|
|
|
|
Reply
|
huffypuffy2k4
|
10/21/2004 2:14:00 PM |
|