mirror of
https://git.savannah.gnu.org/git/emacs.git
synced 2024-12-23 10:34:07 +00:00
Add information about `-fno-crossjumping' for GCC.
This commit is contained in:
parent
1868c863ed
commit
70d9a9cda7
@ -1,3 +1,7 @@
|
||||
2005-03-01 David Kastrup <dak@gnu.org>
|
||||
|
||||
* DEBUG: Add information about `-fno-crossjumping' for GCC.
|
||||
|
||||
2005-02-14 Lute Kamstra <lute@gnu.org>
|
||||
|
||||
* TODO: Remove battery.el entry (DONE).
|
||||
|
@ -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
|
||||
|
Loading…
Reference in New Issue
Block a user