TIL another awful thing about Linux procfs behavior; top-level /proc only reports processes (thread-groups) via getdents/readdir, but opening /proc/$tid where $tid is any thread id (not necessarily also a process id) succeeds.
-
Show this thread
-
Replying to @RichFelker
The second part seems reasonable to me in that it matches everything else (e.g., kill(2) a non-main thread by tid). The first part is backwards compat for stuff like ps(1), I assume.
1 reply 0 retweets 0 likes -
Replying to @xlerb
The argument to kill is a pid, not a tid; it sends the signal to the process not a particular thread of the process. It makes no sense to call it with a tid.
1 reply 0 retweets 0 likes
Replying to @RichFelker @xlerb
The first part is correct. /proc is supposed to list processes; there's no reason for threads to be there.
9:57 AM - 12 Apr 2018
0 replies
0 retweets
0 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.