Cédric Vincent
Cédric Vincent
How to reproduce (on Gandi Simple Hosting): ``` $ uname -r 3.14.25-grsec-paas-738e2ee $ ./proot-v5.0.0 echo OK proot info: pid 1211: terminated with signal 9 $ ./proot-v4.0.3 echo OK OK ```
How to reproduce (host system is Slackware64-current): ``` $ proot gdb ./a.out GNU gdb (GDB) 7.8 [...] (gdb) break main Breakpoint 1 at 0x400629 (gdb) run Starting program: a.out warning:...
How to reproduce: ``` ./src/proot bash -c 'tests/test-c47aeb7d & gdb -p $!' ``` where tests/test-c47aeb7d.c was modified this way: ``` void *print_hello(void *id) { + sleep(999); pthread_exit(id); } ``` Expected...
How to reproduce: ``` shell-1$ /usr/bin/sleep 999 ``` then in another prooted shell: ``` shell-2$ gdb -p [...] (gdb) x /i $pc => 0x7f29946dced0 : cmp $0xfffffffffffff001,%rax (gdb) quit A...
That way, both initial and reproduced executions use the same code (in the standard C library). Today, this can be achieved by setting LD_HWCAP_MASK to 0 before starting CARE.
- Host: Slackware-14.1/Linux-3.10.17/x86_64 - Guest: Ubuntu-13.04/x86 - Command: proot -R ubuntu-13.04-x86 epsxe - Output: proot warning: process 4183 is doing suspicious brk() Running ePSXe emulator version 1.9.4. [...]
Details: https://linuxfr.org/nodes/101156/comments/1518591
Details: http://linuxfr.org/news/care-et-la-reproductibilite-des-executions#comment-1517970
> Yes it is released (version 5.0.0), it crashes Free Pascal that > worked before - apt-get install fp-compiler-2.6.0 crashes with > segfault. I wonder if Gnuroot also suffers from...
How to reproduce: ``` proot-v3.2.2 -w / -r stage3-x32-20140508 true ``` Current result: ``` proot info: pid 21592: terminated with signal 11 ``` Note: this used to work (c.f. commit...