Hello!
I uploaded the first m68k package as of yesterday which I built with
sbuild and qemu-m68k on an amd64 host.
Unfortunately, this package - ruby2.2 - segfaults on Aranym and probably
also real hardware:
root@pacman:~> ruby2.2 --help
Segmentation fault
root@pacman:~>
Now, running this with strace, I made a suspicious observation which
might be related to the the segmentation fault:
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0xef79c0d8} ---
+++ killed by SIGSEGV +++
Segmentation fault
So, it looks like the binary is trying to call prlimit64 which is - as
far as I understand - the 64-bit version of prlimit.
Now, my question is: Is prlimit64 supposed to be used on 32-bit hardware
at all or might this be the result of ruby2.2 being compiled on
qemu-m68k on an amd64 host?
I will rebuild ruby2.2 with qemu-m68k and re-test, this time on an i386
host to find out whether the machine architecture might have had any
influence on this. If yes, this might be a bug in qemu-m68k, isn't it?
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaub...@debian.org
`. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
