I have been setting up continuous integration for various targets based on rust-everywhere. And I’ve hit a block at the
My build failed with:
qemu: Unsupported syscall: 384 running 8 tests /build/buildd/qemu-linaro-1.0.50-2012.03/tcg/tcg.c:1360: tcg fatal error /build/buildd/qemu-linaro-1.0.50-2012.03/tcg/tcg.c:1360: tcg fatal error No output has been received in the last 10 minutes, this potentially indicates a stalled build or something wrong with the build itself.
Now it seems pretty obvious why it works on my box, but fails on TravisCI: I have Debian Testing with qemu 2.5 and Travis has Ubuntu Precise Pangolin with ancient qemu 1.0.50.
However, what I am totally failing to find is what is actually causing triggering the problem.
By searching on LXR I found that on Arm, system call 384 should be [getrandom](http://lxr.free-electrons.com/source/arch/arm/include/
uapi/asm/unistd.h#L413). So I wanted to debug the test locally and see what triggers it. However:
- I can’t find number of that system call on x86_64 either by searching LXR or local
- To a
catch syscall getrandomgdb replies
Unknown syscall name 'getrandom'.
linux/random.hdoes not define function
getrandom, neither in
So I am at loss how to find what is triggering the problem? Does anybody have an idea how to find it?