From xemacs-m  Mon Mar 10 17:28:47 1997
Received: from amber.vis-av.com (amber.vis-av.com [206.119.44.2])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id RAA03906
	for <xemacs-beta@xemacs.org>; Mon, 10 Mar 1997 17:28:45 -0600 (CST)
Received: (from derrell@localhost)
          by amber.vis-av.com (8.8.5/8.8.4)
	  id SAA16815; Mon, 10 Mar 1997 18:28:45 -0500 (EST)
Date: Mon, 10 Mar 1997 18:28:45 -0500 (EST)
Message-Id: <199703102328.SAA16815@amber.vis-av.com>
From: Derrell Lipman <derrell@vis-av.com>
To: xemacs-beta@xemacs.org
Subject: "crashes" with xemacs-19.15b98
Reply-To: derrell@vis-av.com
Mime-Version: 1.0 (generated by tm-edit 7.105)
Content-Type: text/plain; charset=US-ASCII

Twice today, this beta has "crashed" on me.  I call it crash, because
it happens when I don't ask it to.  However, after the first time, I
ran xemacs from gdb, and, after it "crashed" the second time, I saw
that it was a "normal exit" as opposed to a real crash.  I think that
both times, I was doing something from w3, although I'm not positive
of that in either case.  A crash is quite distracting. :-(

I tried to put a breakpoint at exit() or _exit(), but couldn't.  I
noticed that the standard C library is not linked with xemacs.  Where
should I put a breakpoint if I want to catch all (even normal) exits?

Derrell

