Go runtime sometimes does not cooperate and offer a different OS thread for kernel.org/pub/linux/libs/security/libcap/cap.launch execution to fork with.

I've observed one instance (go1.14.4) so far where the runtime sticks in a loop in this state:

(gdb) bt
#0  syscall.rawSyscallNoError ()
    at /home/morgan/sdk/go1.14.4/src/syscall/asm_linux_amd64.s:138
#1  0x00000000004a9b33 in syscall.Gettid (tid=<optimized out>)
    at /home/morgan/sdk/go1.14.4/src/syscall/zsyscall_linux_amd64.go:488
#2  kernel.org/pub/linux/libs/security/libcap/cap.launch (result=0xc0000820c0, 
    attr=0xc0000ba0b0, data=...)
    at /home/morgan/gits/libcap/go/src/kernel.org/pub/linux/libs/security/libcap/cap/launch.go:138
#3  0x000000000045e031 in runtime.goexit ()
    at /home/morgan/sdk/go1.14.4/src/runtime/asm_amd64.s:1373
#4  0x000000c0000820c0 in ?? ()
#5  0x000000c0000ba0b0 in ?? ()
#6  0x0000000000000000 in ?? ()