From xemacs-m  Thu Apr 17 19:20:44 1997
Received: from mailbox2.ucsd.edu (mailbox2.ucsd.edu [132.239.1.54])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id TAA14524
	for <xemacs-beta@xemacs.org>; Thu, 17 Apr 1997 19:20:41 -0500 (CDT)
Received: from sdnp5.ucsd.edu (sdnp5.ucsd.edu [132.239.79.10]) by mailbox2.ucsd.edu (8.8.5/8.6.9) with SMTP id RAA09699 for <xemacs-beta@xemacs.org>; Thu, 17 Apr 1997 17:20:42 -0700 (PDT)
Received: by sdnp5.ucsd.edu (SMI-8.6/SMI-SVR4)
	id RAA02860; Thu, 17 Apr 1997 17:22:06 -0700
To: XEmacs Beta Mailing List <xemacs-beta@xemacs.org>
Subject: Re: The coreless crash phenomenon
References: <9704140220.AA02100@hrs102.rs.kyoto.omronsoft.co.jp> <m2k9m6ruhl.fsf@altair.xemacs.org> <m2encekl0d.fsf@bong.saar.de> <m2iv1phsib.fsf@altair.xemacs.org> <m2zpuz3mwy.fsf@bong.saar.de> <rvsp0repdp.fsf@sdnp5.ucsd.edu> <m2ybaj5bps.fsf_-_@bong.saar.de> <yviaybaizkn7.fsf@atreides.eng.mindspring.net> <m24td5str4.fsf@bong.saar.de>
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: 17 Apr 1997 17:22:06 -0700
In-Reply-To: Marc Aurel's message of 17 Apr 1997 14:45:19 +0200
Message-ID: <rvrag989jl.fsf@sdnp5.ucsd.edu>
Lines: 17
X-Mailer: Gnus v5.4.45/XEmacs 20.1

Marc Aurel <4-tea-2@bong.saar.de> writes:

>   What compiler should XEmacs be built with?              gcc -m486 -g -O4 -malign-jumps=2 -malign-loops=2 -malign-functions=2

I'm not sure what gcc version you are using.  Is it one without the
strength reduction bug?  -fno-strength-reduce will turn that off, I
think.

However, you should still be getting cores. :)

You might try running `gdb xemacs' (with the right path to your xemacs)
and setting a breakpoint with `break fatal_error_signal'.  Then start it
up with `run ARGS' where ARGS is whatever you normally use on the
command line.  When you quit (or it dies) you should get dropped back in
the debugger.  You should be able to type `where' and get a stack trace.
You can type `c' to continue from this point, and it'll generate it's
normal message about crashing and autosave everything, etc.

