You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I'm trying to use the sandbox. When running it on a very simple bash script it seems to segfault once in a while, but not every time. ./sandbox /lib64/ld-linux-x86-64.so.2 /bin/bash breakWithShell.sh
breakWithShell.sh:
#!/bin/bash
/bin/bash ./breakWithShell2.sh
wait
breakWithShell2.sh:
#!/bin/bash
echo "Hello from child shell!"
Error: ./sandbox /lib64/ld-linux-x86-6…” terminated by signal SIGSEGV (Address boundary error).
From /var/log/kern.log:
kernel: [ 1437.685581] sandbox[2215]: segfault at ffffffffffffff78 ip 0000000070005a0e sp ffffffffffffff80 error 7 in sandbox[70000000+f000]
The instruction pointer points to __dune_retry as expected.
Running it multiple times under gdb I can eventually cause an ever worse error that creates an unkillable process. The OS refuses to restart and a hard reset on the computer is required.
The /var/long/kern.log output is pretty long (attached).
This is a minimal example of this bug that I have witnessed in other places as well. Any feedback on what might be causing the bug is greatly appreciated.
Hello, I'm trying to use the sandbox. When running it on a very simple bash script it seems to segfault once in a while, but not every time.
./sandbox /lib64/ld-linux-x86-64.so.2 /bin/bash breakWithShell.sh
breakWithShell.sh:
breakWithShell2.sh:
Error:
./sandbox /lib64/ld-linux-x86-6…” terminated by signal SIGSEGV (Address boundary error).
From
/var/log/kern.log
:The instruction pointer points to
__dune_retry
as expected.Running it multiple times under
gdb
I can eventually cause an ever worse error that creates an unkillable process. The OS refuses to restart and a hard reset on the computer is required.The
/var/long/kern.log
output is pretty long (attached).This is a minimal example of this bug that I have witnessed in other places as well. Any feedback on what might be causing the bug is greatly appreciated.
kernelBug.txt
The text was updated successfully, but these errors were encountered: