FYI, process 255 here is csh. In this case, getty isn't also blocked in
trying to get pgrpsess:
db> ps
pid proc addruid ppid pgrp flag stat wmesg wchan cmd
255 c9735300 c97550000 254 255 0006002 3 ttywai c1b2ea74 csh
254 c9734d00 c97710000 248 254 000400
Found it:
db> show locks 255
exclusive (sx) pgrpsess (0xc03dc0e0) locked @
/cboss/p4/rwatson/trustedbsd/mac/sys/kern/kern_exit.c:234
db> trace 255
mi_switch(0,c1b2ea28,c9735300,c0232341,1) at mi_switch+0x17c
msleep(c1b2ea74,0,15a,c038743f,7530) at msleep+0x31a
ttysleep(c1b2ea28,c1b2ea74,15a,c0387
Some more details, now I have WITNESS compiled in...
crash1# script ls
Script started, output file is ls
crash1#
crash1# exitStopped at siointr1+0xf2: movl$0,brk_state1.702
db> trace
siointr1(c185f400,c0446ec0,0,c03a0260,662) at siointr1+0xf2
siointr(c185f400,18,c86c0010,c0230010,0) a
I can reproduce this on a 5.0-CURRENT from yesterday, although I do appear
to be able to break into the serial debugger. I get the following:
db> ps
pid proc addruid ppid pgrp flag stat wmesg wchan cmd
1955 c9737600 c97790000 1954 1955 0006002 3 ttywai c1bd8074 csh
cvs checkout -D "8PM last Monday" :-)
(or similar)
On Fri, 8 Mar 2002, David Wolfskill wrote:
> Is anyone else seeing this?
>
> Running -CURRENT (been tracking it daily for a while, now), I find that
> if I run script(1), things basically run as expected... until I try to
> close script's
