Re: qemu-m68k and prlimit64 - segfaults
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> writes:
> 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} ---
Why do you think there is any relation between these two events?
> 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?
The prlimit function is implemented by the prlimit64 syscall. There is
no other way to implement it.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
Reply to: