* trouble.texi (Crashing): Document ulimit -c.

diff --git a/doc/emacs/ChangeLog b/doc/emacs/ChangeLog
index 8d3fc2b3e0c4701bbdb13e59ab39e710e8666714..28d6d2865a8e0c4c6a6b0d90aeb9fbf1ed02646d 100644 (file)
--- a/doc/emacs/ChangeLog
+++ b/doc/emacs/ChangeLog
@@ -1,3 +1,7 @@
+2012-09-22  Paul Eggert  <eggert@cs.ucla.edu>
+
+       * trouble.texi (Crashing): Document ulimit -c.
+
 2012-09-21  Paul Eggert  <eggert@cs.ucla.edu>
 
        * trouble.texi (Crashing): Document addr2line.

diff --git a/doc/emacs/trouble.texi b/doc/emacs/trouble.texi
index ad270aec232982a8e75c11c8ba6df4a33aa21715..1c45287cdaaecd5c98b475c231c8e94b332d7204 100644 (file)
--- 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: