[Emacs-diffs] /srv/bzr/emacs/trunk r110147: * trouble.texi (Crashing): Document ulimit -c.

[Paul Eggert]

------------------------------------------------------------
revno: 110147
committer: Paul Eggert <address@hidden>
branch nick: trunk
timestamp: Sat 2012-09-22 12:27:25 -0700
message:
  * trouble.texi (Crashing): Document ulimit -c.
modified:
  doc/emacs/ChangeLog
  doc/emacs/trouble.texi

=== modified file 'doc/emacs/ChangeLog'
--- a/doc/emacs/ChangeLog       2012-09-21 19:28:41 +0000
+++ b/doc/emacs/ChangeLog       2012-09-22 19:27:25 +0000
@@ -1,3 +1,7 @@
+2012-09-22  Paul Eggert  <address@hidden>
+
+       * trouble.texi (Crashing): Document ulimit -c.
+
 2012-09-21  Paul Eggert  <address@hidden>
 
        * trouble.texi (Crashing): Document addr2line.

=== modified file 'doc/emacs/trouble.texi'
--- a/doc/emacs/trouble.texi    2012-09-21 19:28:41 +0000
+++ b/doc/emacs/trouble.texi    2012-09-22 19:27:25 +0000
@@ -282,10 +282,15 @@
 @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
address@hidden  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
address@hidden  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: