Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 17 Dec 1996 21:36:27 +1100
From:      Bruce Evans <bde@zeta.org.au>
To:        bugs@freebsd.org, swallace@ece.uci.edu
Cc:        dawes@xfree86.org
Subject:   Re: unexpected signal 2?
Message-ID:  <199612171036.VAA18150@godzilla.zeta.org.au>

next in thread | raw e-mail | index | archive | help
>   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



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