Re: Unkillable process

From: Vladimir Grebenschikov <vova_at_sw.ru>
Date: Thu, 28 Oct 2004 00:34:28 +0400
В ср, 27/10/2004 в 15:31 -0400, Ken Smith пишет:
> On Wed, Oct 27, 2004 at 04:37:27PM +0400, Vladimir Grebenschikov wrote:
> 
> > Looks like I should upgrade to 1.251:
> > 
> > diff -u -r1.251 -r1.250
> > --- sys/kern/kern_exit.c        23 Oct 2004 11:20:26 -0000      1.251
> > +++ sys/kern/kern_exit.c        5 Oct 2004 18:51:11 -0000       1.250
> > _at__at_ -403,7 +403,7 _at__at_
> >                  * since their existence means someone is screwing up.
> >                  */
> >                 if (q->p_flag & P_TRACED) {
> > -                       q->p_flag &= ~(P_TRACED | P_STOPPED_TRACE);
> > +                       q->p_flag &= ~P_TRACED;
> >                         psignal(q, SIGKILL);
> >                 }
> 
> Yes, but before you do... :-)
> 
> If it's not too late can you do:
> 
> 	ps -o f -l
> 
> Or if anyone "succeeds" at wedging processes (especially if you
> already have the above patch applied) can you try this?

Sorry, it is too late, also I had no patch applied.
I guess my case can be reproduced by killing -KILL gdb attached to
stopped process. With updated kernel process being debugged disapper
with gdb.

> I have a trivial procedure that produces unkillable processes
> before the above patch, and this patch fixes that case.  I've got
> one person reporting that he can still get wedged processes even
> with the above patch though so I'm looking for a bit more information.
> 
> Thanks...
> 
-- 
Vladimir B. Grebenschikov
SWsoft Inc. vova_at_sw-soft.com
Received on Thu Oct 28 2004 - 06:19:55 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:19 UTC