3 ms·

I have zero insight obviously but I still believe it was ptrace that broke the camels back. And yes, I had so much hope for WSL1. > ptrace(PTRACE_TRACEME, 0, 0

by chx 6y ago

I have zero insight obviously but I still believe it was ptrace that broke the camels back. And yes, I had so much hope for WSL1. > ptrace(PTRACE_TRACEME, 0, 0, 0) = -1 EPERM (Operation not permitted) Issues also exist for PTRACE_O_TRACEEXIT, PTRACE_O_TRACEEXEC, PTRACE_OLDSETOPTIONS, PTRACE_SYSEMU.

shawnz 6y ago
It seems like those bugs were fixed some time ago. See: https://github.com/microsoft/WSL/issues/555 https://github.com/microsoft/WSL/issues/555
- chx 6y ago
  The big one is https://github.com/microsoft/WSL/issues/2028 https://github.com/microsoft/WSL/issues/2028 which is "fixed-in-wsl2" This makes lldb and dlv both just not work in wsl1 and that's just the languages I dabbed in, I think the Swift debugger had issues as well.
  - shawnz 6y ago
    Interesting, you are right I can repro the bug in issue 2028 although 555 claims to be fixed.