From xemacs-m  Thu Jan 23 20:57:40 1997
Received: from UCSD.EDU (mailbox2.ucsd.edu [132.239.1.54])
          by xemacs.org (8.8.4/8.8.4) with ESMTP
	  id UAA19073 for <xemacs-beta@xemacs.org>; Thu, 23 Jan 1997 20:57:39 -0600 (CST)
Received: from sdnp5.ucsd.edu (sdnp5.ucsd.edu [132.239.79.10]) by UCSD.EDU (8.8.3/8.6.9) with SMTP id SAA24358 for <xemacs-beta@xemacs.org>; Thu, 23 Jan 1997 18:57:38 -0800 (PST)
Received: by sdnp5.ucsd.edu (SMI-8.6/SMI-SVR4)
	id SAA04237; Thu, 23 Jan 1997 18:55:11 -0800
Sender: dmoore@sdnp5.ucsd.edu
To: XEmacs Beta Mailing List <xemacs-beta@xemacs.org>
Subject: Re: Ebola warning in b91
References: <199701240221.VAA11413@spacely.icd.teradyne.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
From: David Moore <dmoore@UCSD.EDU>
Date: 23 Jan 1997 18:55:09 -0800
In-Reply-To: Vinnie Shelton's message of Thu, 23 Jan 1997 21:21:13 -0500
Message-ID: <rvu3o7srxu.fsf@sdnp5.ucsd.edu>
Lines: 47
X-Mailer: Red Gnus v0.80/XEmacs 19.15

Vinnie Shelton  <shelton@icd.teradyne.com> writes:

> There I was, happily plugging away with 20-b91, creating frames as happy as 
> could be.  At some point, I noticed the following on the xterm whence my 
> xemacs was started:
> 
> Ebola warning!! (0 and ?\()
>    [memq, #<subr make-frame (interactive)>, call-interactively]
> Ebola warning!! (0 and ?\[)
>    [memq, #<subr make-frame (interactive)>, call-interactively]
> Ebola warning!! (0 and ?\{)
>    [memq, #<subr make-frame (interactive)>, call-interactively]
> 
> Now, the only remotely unusual thing about these frames is that they have 
> only one minibuffer - on the first frame.
> 
> Has anyone else seen this?

	Something is trying to compare an int to a character,
unfortunately it's not providing enough information (at least for me,
maybe someone else can see it :).  If possible, can you run xemacs in
gdb, and set a breakpoint on eq_with_ebola_notice, and when it stops
there, send in the C stack trace.


1. Start gdb as `gdb xemacs' (or whatever path you give to emacs to
normally start it).

2. Type `break eq_with_ebola_notice'

3. Start xemacs with `run ARGS' were ARGS are whatever you normally give
after xemacs, like -display.

4. Once you hit the ebola bug, gdb will wake up.  Type `where' and mail
in that list.

5. You can either press `cont' to continue, in which case you'll stop
again on the next occurance.  Or you can `quit'.  Or you can do `clear
eq_with_ebola_notice' followed by `cont' which will have it not stop
anymore, and you can then quit your emacs normally.


-- 
David Moore <dmoore@ucsd.edu>       | Computer Systems Lab      __o
UCSD Dept. Computer Science - 0114  | Work: (619) 534-8604    _ \<,_
La Jolla, CA 92093-0114             | Fax:  (619) 534-1445   (_)/ (_)
<URL:http://oj.egbt.org/dmoore/>    | In a cloud bones of steel.

