From 70d9a9cda7366457785c6031d0f09544131a786a Mon Sep 17 00:00:00 2001 From: David Kastrup Date: Tue, 1 Mar 2005 16:01:05 +0000 Subject: [PATCH] Add information about `-fno-crossjumping' for GCC. --- etc/ChangeLog | 4 ++++ etc/DEBUG | 9 ++++++++- 2 files changed, 12 insertions(+), 1 deletion(-) diff --git a/etc/ChangeLog b/etc/ChangeLog index e357de8121a..26ce127e1bd 100644 --- a/etc/ChangeLog +++ b/etc/ChangeLog @@ -1,3 +1,7 @@ +2005-03-01 David Kastrup + + * DEBUG: Add information about `-fno-crossjumping' for GCC. + 2005-02-14 Lute Kamstra * TODO: Remove battery.el entry (DONE). diff --git a/etc/DEBUG b/etc/DEBUG index b242d1d028d..fe3bde0c3b8 100644 --- a/etc/DEBUG +++ b/etc/DEBUG @@ -1,5 +1,5 @@ Debugging GNU Emacs -Copyright (c) 1985, 2000, 2001 Free Software Foundation, Inc. +Copyright (c) 1985, 2000, 2001, 2005 Free Software Foundation, Inc. Permission is granted to anyone to make or distribute verbatim copies of this document as received, in any medium, provided that the @@ -20,6 +20,13 @@ document.] where the executable was made. That directory has a .gdbinit file that defines various "user-defined" commands for debugging Emacs. +** When you are trying to analyze failed assertions, it will be +essential to compile Emacs either completely without optimizations or +at least (when using GCC) with the -fno-crossjumping option. Failure +to do so may make the compiler recycle the same abort call for all +assertions in a given function, rendering the stack backtrace useless +for identifying the specific failed assertion. + ** It is a good idea to run Emacs under GDB (or some other suitable debugger) *all the time*. Then, when Emacs crashes, you will be able to debug the live process, not just a core dump. (This is especially -- 2.11.4.GIT