Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 2 Jul 2002 21:02:33 -0400 (EDT)
From:      Andrew Gallatin <gallatin@cs.duke.edu>
To:        Julian Elischer <julian@elischer.org>
Cc:        freebsd-current@freebsd.org
Subject:   Re: KSE signal problems still
Message-ID:  <15650.19753.171293.625675@grasshopper.cs.duke.edu>
In-Reply-To: <Pine.BSF.4.21.0207021748130.97650-100000@InterJet.elischer.org>
References:  <15650.13062.63024.716217@grasshopper.cs.duke.edu> <Pine.BSF.4.21.0207021748130.97650-100000@InterJet.elischer.org>

next in thread | previous in thread | raw e-mail | index | archive | help

Julian Elischer writes:
 > 
 > 
 > On Tue, 2 Jul 2002, Andrew Gallatin wrote:
 > 
 > > 
 > > Julian Elischer writes:
 > >  > 
 > >  > 
 > >  > On Tue, 2 Jul 2002, Andrew Gallatin wrote:
 > >  > 
 > >  > > 
 > >  > > An easy way to induce a panic w/a post KSE -current is to ^C gdb as it
 > >  > > starts on an SMP machine:
 > >  > 
 > >  > A possibly related breakage is:
 > >  > 
 > >  > type ^Z while doing "make buiildworld" (or something similar).
 > >  > 
 > >  > when you type 'fg' there is a high change the build will abort..
 > >  > 
 > > 
 > > This is nearly 100% for me.  But only on MP boxes.  On my uniprocessor
 > > alpha, things work just fine.  Oh.. hmm.. I'm not sure if I have
 > > witless compiled in there.. 
 > 
 > which is almost 100%,? the ^Z killing the process, or ^C killing the
 > machine?

^C killing the machine.

Drew

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15650.19753.171293.625675>