truss(1) locked in kernel with 8.0-BETA2
Stefan Bethke
stb at lassitu.de
Sat Aug 22 20:03:35 UTC 2009
Am 22.08.2009 um 20:58 schrieb Jeremie Le Hen:
> The same thing can happen with dialog(1); truss shows:
> % read(0,0xbfbfcf10,1) = 0 (0x0)
> % read(0,0xbfbfcf10,1) = 0 (0x0)
> % read(0,0xbfbfcf10,1) = 0 (0x0)
> % read(0,0xbfbfcf10,1) = 0 (0x0)
>
> And so on. And after ^C the processes are staled in the same state in
> the kernel.
I've noticed the dialog issue some years ago, and finally managed to
put a patch together. See PR#137665.
Stefan
--
Stefan Bethke <stb at lassitu.de> Fon +49 151 14070811
More information about the freebsd-current
mailing list