Hi, On Wed, May 25, 2011 at 4:10 PM, Arnaud Lacombe <lacombar_at_gmail.com> wrote: > I'm now trying to track down the original instruction triggering the > SIGILL, but it is in a library and that section of the memory does not > seem to be included in the core. Moreover I do not think I have any > way on a broken system to get the address at which libraries get > loaded (understand that ldd(1) is dynamically linked, and as the libc > the likely culprit, rendering ldd(1) useless). > ok, the reason the whole system appears broken is because `/libexec/ld-elf.so.1' is broken, it contains several CMOV instructions. The objects it is made from are clear from any CMOV, so this code likely comes from the jail's lib. I guess that the responsible for building the jail environment had the wonderful idea to use the host /usr/lib32 and put them in the jail /usr/lib, without knowing that those libraries are i686-optimized, That also explain the /boot/loader brokenness which links against the jail's libstand.a. - ArnaudReceived on Wed May 25 2011 - 19:49:24 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:14 UTC