From 2e83df57be5105f0fee8e6fe8360e75844ecfb7b Mon Sep 17 00:00:00 2001 From: Paul Eggert Date: Sat, 22 Sep 2012 12:27:25 -0700 Subject: [PATCH] * trouble.texi (Crashing): Document ulimit -c. --- doc/emacs/ChangeLog | 4 ++++ doc/emacs/trouble.texi | 13 +++++++++---- 2 files changed, 13 insertions(+), 4 deletions(-) diff --git a/doc/emacs/ChangeLog b/doc/emacs/ChangeLog index 8d3fc2b3e0c..28d6d2865a8 100644 --- a/doc/emacs/ChangeLog +++ b/doc/emacs/ChangeLog @@ -1,3 +1,7 @@ +2012-09-22 Paul Eggert + + * trouble.texi (Crashing): Document ulimit -c. + 2012-09-21 Paul Eggert * trouble.texi (Crashing): Document addr2line. diff --git a/doc/emacs/trouble.texi b/doc/emacs/trouble.texi index ad270aec232..1c45287cdaa 100644 --- a/doc/emacs/trouble.texi +++ b/doc/emacs/trouble.texi @@ -282,10 +282,15 @@ itself, and the reserve supply may not be enough. @subsection When Emacs Crashes Emacs is not supposed to crash, but if it does, before it exits it -reports some information about the crash to the standard error stream -@code{stderr}. This report may be useful to someone who later debugs -the same version of Emacs on the same platform. The format of this -report depends on the platform, and some platforms support backtraces. +reports a brief summary of the crash to the standard error stream +@code{stderr}. If enabled, a crashed Emacs also generates a core dump +containing voluminous data about the crash. On many platforms you can +enable core dumps by putting the shell command @samp{ulimit -c unlimited} +into your shell startup script. The crash report and core dump can be +used when debugging the same version of Emacs on the same platform. + +The format of the crash report depends on the platform, and some +platforms support backtraces. Here is an example, generated on x86-64 GNU/Linux with version 2.15 of the GNU C Library: -- 2.11.4.GIT