First thread in proc in not passed to thread_dtor eventhandler upon exit
Hans Petter Selasky
hps at selasky.org
Sat Feb 18 21:40:45 UTC 2017
Is the following a bug or feature. I observe that the first thread in a
procedure is not passed to thread_dtor as declared by the following
eventhandler, when the procedure exits.
Is this a bug or feature?
I see a couple of clients in the kernel and if the first thread in proc
is simply recycled by re-init, we're leaking data for these clients?
And I'm planning to add one more for the LinuxKPI.
More information about the freebsd-current