From xemacs-m  Wed Dec 11 09:55:08 1996
Received: from gnosis.slac.com (pilone@gnosis.bevc.blacksburg.va.us [198.82.216.37]) by xemacs.cs.uiuc.edu (8.8.3/8.8.3) with SMTP id JAA29150 for <xemacs-beta@xemacs.org>; Wed, 11 Dec 1996 09:55:07 -0600 (CST)
Received: (from pilone@localhost) by gnosis.slac.com (8.6.12/8.6.9) id KAA20708; Wed, 11 Dec 1996 10:58:10 -0500
Date: Wed, 11 Dec 1996 10:58:10 -0500
Message-Id: <199612111558.KAA20708@gnosis.slac.com>
From: Dan Pilone <pilone@gnosis.slac.com>
To: xemacs-beta@xemacs.org
Subject: Re: make-frame-on-display crashing bug 19.15-b3 & 19.14
In-Reply-To: <rvbuc1y2dx.fsf@sdnp5.ucsd.edu>
References: <rvbuc1y2dx.fsf@sdnp5.ucsd.edu>
Mime-Version: 1.0 (generated by tm-edit 7.92)
Content-Type: text/plain; charset=US-ASCII

Previously written in blue crayon:
 > 
 > 	I can reliably crash under solaris 2.* when starting xemacs
 > with -nw and executing 'make-frame-on-display' to a nonexistant host.
 > The next call to make-frame-on-display with a valid host results in the
 > following core.

	I can also crash 19.14, 19.15b2, and 20b30 (w/o Mule) by
creating a frame on the other display then exiting through the first
frame using C-xC-c.  This appears on an SGI under both Irix 5.3 and
Irix 6.2.  I started tracing it but ran out of time.  I'll try and
look again. -- Dan

