michalbednarski

I haven't tested proot under WSL, but you should be able to install libtalloc-dev through apt

Looks like there was odd number of `SIGTRAP|0x80` events emitted to strace. Was this on 32bit arm kernel with version >=4.8? (Because if so I might know what happened, although...

Unfortunately I couldn't get device to reproduce this on, so I can only provide generic advice to try: 1. Update packages inside guest (`pacman -Syu`, Arch doesn't support mixed old/new...

Second argument of execve is `char **`, (pointer/array terminated with NULL to pointers to strings (`\0` terminated array of `char`s) Your `*harg` contains now address (in tracee memory) of `argv[0]`,...

You mean Linux >=4.8 support? (47138da843bbfcea2273a11ce9d83b40031465bf and follow-up commit as that one wasn't complete fix) I've also got workarounds for Android Oreo seccomp policy (which blocks syscalls such as `open(2)`...

I've tried `fix-seccomp` branch form proot-me/proot repo (for which CI builds you've linked, not the linked pull request) and so far I've found one thing that needs to be fixed:...

I've found another issue in proot-me/proot/fix-seccomp: The `handle_tracee_event` function is called in multiple places, however only one of them has check for kernel version and call `handle_tracee_event_kernel_4_8`, code in `ptrace.c`...

One more thing I've forgot to write: test which nest proot (`proot proot -0 id`) fail because proot doesn't pass seccomp events to tracees and you new implementation considers seccomp...

So far I couldn't reproduce this locally Looks like `tar` has crashed before it finished loading dynamic libraries, so this shouldn't be related to arguments, just `proot --link2symlink tar` should...

I'm asking if just running `proot --link2symlink tar` is causing crash (or does it show `tar`-s help message) If so, I'd ask for: 1. `/apex/com.android.runtime/bin/linker` file from that device 2....