From xemacs-m  Tue Apr  8 11:17:21 1997
Received: from mailbox1.ucsd.edu (mailbox1.ucsd.edu [132.239.1.53])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id LAA03277
	for <xemacs-beta@xemacs.org>; Tue, 8 Apr 1997 11:17:21 -0500 (CDT)
Received: from sdnp5.ucsd.edu (sdnp5.ucsd.edu [132.239.79.10]) by mailbox1.ucsd.edu (8.8.5/8.6.9) with SMTP id JAA19948 for <xemacs-beta@xemacs.org>; Tue, 8 Apr 1997 09:17:22 -0700 (PDT)
Received: by sdnp5.ucsd.edu (SMI-8.6/SMI-SVR4)
	id JAA04189; Tue, 8 Apr 1997 09:18:57 -0700
Sender: dmoore@sdnp5.ucsd.edu
To: xemacs-beta@xemacs.org
Subject: Re: 19.15: PATCH for multi-device core dump
References: <9704080635.AA17778@GS213.SP.CS.CMU.EDU> <QQckka25124.199704081504@crystal.WonderWorks.COM>
X-Face: "oX;zS#-JU$-,WKSzG.1gGE]x^cIg!hW.dq>.f6pzS^A+(k!T|M:}5{_%>Io<>L&{hO7W4cicOQ|>/lZ1G(m%7iaCf,6Qgk0%%Bz7b2-W3jd0m_UG\Y;?]}4s0O-U)uox>P3JN)9cm]O\@,vy2e{`3pb!"pqmRy3peB90*2L
Mail-Copies-To: never
Mime-Version: 1.0 (generated by tm-edit 7.106)
Content-Type: text/plain; charset=US-ASCII
From: David Moore <dmoore@ucsd.edu>
Date: 08 Apr 1997 09:18:56 -0700
In-Reply-To: Kyle Jones's message of Tue, 8 Apr 1997 11:04:49 -0400 (EDT)
Message-ID: <rvzpv9wkr3.fsf@sdnp5.ucsd.edu>
Lines: 23
X-Mailer: Gnus v5.4.40/XEmacs 20.1(beta11)

Kyle Jones <kyle_jones@wonderworks.com> writes:

> Darrell Kindred writes:
>  > The following causes a core dump in XEmacs 19.15 under all
>  > OSes I've tried:
>  > 
>  >     xemacs -nw -q
>  >     M-x make-frame-on-display myhost:0
>  > 
>  > (where myhost:0 is a valid display).  The problem is that
>  > extract_xpm_color_names() instantiates specifiers using the
>  > selected window (rather than the appropriate device) as the
>  > domain.
> 
> I submitted the patch that makes the code do this.  The bug I
> was fixing is that local colors were ignored when instantiating
> XPM images.  So if an XPM had a transparant background, it would
> not be matched against the buffer, window or frame background color.

> I would prefer to find a way not to apply this.

I'd suggest thinking about how to solve this.  There've been about 5
crash reports to crashes@xemacs.org about this in the past two weeks.

