Bug #2816
openA multitasking process being debugged can get stuck
0%
Description
957986 phma 0 64M 4372K wait 0 0:01 0:01 0.00% gdb
957987 phma 0 34M 1756K killlwps 1 0:00 0:00 0.00% aoeu
999533 phma 0 34M 3772K kqread 0 0:00 0:00 0.00% sshd
999602 phma 0 15M 2312K CPU1 1 0:00 0:00 0.00% top
999534 phma 0 14M 3276K wait 1 0:00 0:00 0.00% bash
Running top -t shows that the program has one thread in killlwps state and one in STOP state. There is apparently no way to restart the stopped thread, or to kill the process. There is no explanation in "man top" of what killlwps is. "apropos killlwps" returns nothing.
I'm not sure whether to put this in documentation (because there's no explanation of killlwps) or something else (if there's no way to kill the process).
No data to display