[WSL1] valgrind return"unsupported arch_prctl option"

[Po-wei]

Please fill out the below information:

• Your Windows build number: (Type ver at a Windows Command Prompt)
  Microsoft Windows [Version 10.0.18363.476]

• What you're doing and what's happening: (Copy&paste the full set of specific command-line steps necessary to reproduce the behavior, and their output. Include screen shots if that helps demonstrate the problem.)
  run valgrind

• What's wrong / what should be happening instead:

always return error calling PR_SET_PTRACER, vgdb might block

• Strace of the failing command, if applicable: (If some_command is failing, then run strace -o some_command.strace -f some_command some_args, and link the contents of some_command.strace in a gist here).
  https://gist.github.com/Po-wei/7b2228c689fa33c847bf95874964b2f2

• For WSL launch issues, please collect detailed logs.

[therealkenc]

Copy&paste the full set of specific command-line steps necessary to reproduce the behavior

run valgrind

That wasn't your repro. Do appreciate the strace(1) logs tho.

execve("/usr/bin/valgrind", ["valgrind", "./ixtest_01"], 0x7fffc2e543f0 /* 21 vars */) = 0
[...]
34    mmap(0x1002bb1000, 27597024, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, 0, 0) = 0x1002bb1000
34    mmap(0x1004603000, 4769856, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, 0, 0) = 0x1004603000
34    mmap(0x1004a90000, 1362816, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, 0, 0) = 0x1004a90000
34    mmap(0x1004bdd000, 131042, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, 0, 0) = 0x1004bdd000
34    mmap(0x1004bfd000, 65536, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, 0, 0) = 0x1004bfd000
34    write(1027, "\nvalgrind: the 'impossible' happ"..., 71) = 71
34    gettid()                          = 34
34    write(1027, "\nhost stacktrace:\n", 18) = 18

There's a few google hits. Dunno if they apply (probably not). valgrind has/had been reported to work at some point ref #120. Guidance would be to try WSL2.

[Po-wei]

prior to 1909, I can run valgrind with very very same program in WSL1.
I guess some windows update patch leads to this bug.

[Po-wei]

./a.out is a simple C++ hello_world just return 0;

[Po-wei]

manual compile the latest version of valgrind fix the problems