From owner-freebsd-bugs  Tue Dec 17 02:45:37 1996
Return-Path: <owner-bugs>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id CAA14303
          for bugs-outgoing; Tue, 17 Dec 1996 02:45:37 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id CAA14298
          for <bugs@freebsd.org>; Tue, 17 Dec 1996 02:45:30 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id VAA18150; Tue, 17 Dec 1996 21:36:27 +1100
Date: Tue, 17 Dec 1996 21:36:27 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199612171036.VAA18150@godzilla.zeta.org.au>
To: bugs@freebsd.org, swallace@ece.uci.edu
Subject: Re: unexpected signal 2?
Cc: dawes@xfree86.org
Sender: owner-bugs@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>   743 AnsiTermT CALL  kill(0xffffffff,0x2)
>   743 AnsiTermT PSIG  SIGHUP caught handler=0x4600 mask=0x2 code=0x0

>I don't know why this simple user-level program is causing
>my X server to die.  I've u/ld the binary to freefall.

Bug in AnsiTerm.  You can shoot yourself in the foot just as easily
using `kill -HUP -1' or `kill -HUP 0'.

>Also, I've always had this annonying problem using a PS/2 mouse,
>which is why I end up using a serial one.  When I use device
>/dev/psm0 and protocol PS/2, sometimes the keyboard state gets messed
>up so that the X server thinks a modifier key (control, alt) will 
>remain in the depressed state when the key is not pressed.  I

This should work better in FreeBSD-current and -2.2.  The psm and
syscons drivers can now separate psm and keyboard scancodes.

Bruce