-
Notifications
You must be signed in to change notification settings - Fork 378
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
proot info: pid 19967: terminated with signal 31 #134
Comments
Same here with both 5.0.0 and latest master. Actually, it seems to fail even without using the qemu-arm-static part. It fails both with and without PROOT_NO_SECCOMP=1.
|
proot crashes with current jenkins node setup, which means we cannot use it to run ARM based axis. proot bug is already reported upstream in: proot-me/proot#134 Related: OS#3061 Change-Id: I9bc48349c78f395b3842bc5caaf6e948fb4c299e
Is this also related?
|
@cswl no it doesn't seems related. You have a segfault but the original error is a "bad syscall". @pespin @liuchibing Maybe you could try to give us some gdb output, about what is currently run when we got this signal. |
@alkino How am I supposed to run gdb on it, isn't proot already using ptrace on vpid 1? as far as i know you cannot ptrace a process from several different processes right? |
Hum sorry, you're right. |
@liuchibing @cswl please test with the latest v5.3.0 release. |
When I run proot on a aarch64 cpu, i got this:
Is there any solutions?
The text was updated successfully, but these errors were encountered: