[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Emacs-diffs] Changes to emacs/etc/DEBUG
From: |
David Kastrup |
Subject: |
[Emacs-diffs] Changes to emacs/etc/DEBUG |
Date: |
Tue, 01 Mar 2005 11:01:08 -0500 |
Index: emacs/etc/DEBUG
diff -c emacs/etc/DEBUG:1.31 emacs/etc/DEBUG:1.32
*** emacs/etc/DEBUG:1.31 Sun Feb 6 10:38:49 2005
--- emacs/etc/DEBUG Tue Mar 1 16:01:05 2005
***************
*** 1,5 ****
Debugging GNU Emacs
! Copyright (c) 1985, 2000, 2001 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
--- 1,5 ----
Debugging GNU Emacs
! 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,25 ****
--- 20,32 ----
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
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Emacs-diffs] Changes to emacs/etc/DEBUG,
David Kastrup <=