Path: utzoo!mnetor!uunet!iscuva!jimc
From: jimc@iscuva.ISCS.COM (Jim Cathey)
Newsgroups: comp.emacs
Subject: Re: Core dump on Pyramid
Message-ID: <1279@iscuva.ISCS.COM>
Date: 28 Mar 88 21:03:04 GMT
References: <2692@calmasd.GE.COM> <2698@calmasd.GE.COM>
Organization: ISC Systems Corporation, Spokane, WA
Lines: 38
Keywords: Emacs core dump on Pyramid

In article <2698@calmasd.GE.COM> dko@calmasd.UUCP (Dan O'Neill) writes:
>In a previous message I described a problem in running a unix version
>of GNU Emacs over a DEC LAT box to a tty.  The DEC LAT box would
>complain about something, send out a stream of ^G's and thus force GNU
>Emacs to core dump.  This is not a problem for VMS versions of GNU Emacs.
>
>As it turns out, this was a hardware configuration problem.  The
>solution is to set the parameters on the LAT box connected to the unix
>box (in our case a Pyramid machine) as follows:
>
>		old setting		correct setting
>
>Character size:	   7 bits		   8 bits
>Parity:		   Even			   None
>
>
>The LAT will now transfer all of the data between the terminal and the
>host.

Possibly it wasn't sending ^G at all.  One of our 18.48 builds on a
SYSV style system was messed up in that meta-DEL generated a ^G
(according to emacs).  What was happening was that VINTR and VQUIT were
set to 0xFF, which caused a SIGINT and/or SIGQUIT to be sent on m-DEL.
SIGINT/SIGQUIT are interpreted as ^G (abort) by emacs, so perhaps you
were having something similar happen (parity widgets being interpreted
as meta-whatevers), or other sources of SIGQUITs.  The SVID I've seen
recommends that you set VINTR to 0xFF or other 'illegal' character when
you don't want SIGINT rather than providing a real 'off' mechanism.
Humpph, illegal indeed!  

+----------------+
! II      CCCCCC !  Jim Cathey
! II  SSSSCC     !  ISC Systems Corp.
! II      CC     !  TAF-C8;  Spokane, WA  99220
! IISSSS  CC     !  UUCP: uunet!iscuva!jimc
! II      CCCCCC !  (509) 927-5757
+----------------+
			"With excitement like this, who is needing enemas?"