aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRichard M. Stallman2001-06-29 03:20:46 +0000
committerRichard M. Stallman2001-06-29 03:20:46 +0000
commitc6fcb73d2a8b2f024885ff52654622b56e993e4e (patch)
tree0e7ab15c19e2ab900c45cdc21877c4286efa1da9
parentb2683503ad70ffadb4699fc28d37877350911321 (diff)
downloademacs-c6fcb73d2a8b2f024885ff52654622b56e993e4e.tar.gz
emacs-c6fcb73d2a8b2f024885ff52654622b56e993e4e.zip
Explain why don't mail a core dump.
-rw-r--r--man/trouble.texi9
1 files changed, 9 insertions, 0 deletions
diff --git a/man/trouble.texi b/man/trouble.texi
index 514fa9f1a20..42813357426 100644
--- a/man/trouble.texi
+++ b/man/trouble.texi
@@ -849,6 +849,15 @@ However, simplification is not vital; if you can't do this or don't have
849time to try, please report the bug with your original test case. 849time to try, please report the bug with your original test case.
850 850
851@item 851@item
852A core dump file.
853
854Debugging the core dump might be useful, but it can only be done on
855your machine, with your Emacs executable. Therefore, sending the core
856dump file to the Emacs maintainers won't be useful. Above all, don't
857include the core file in an email bug report! Such a large message
858can be extremely inconvenient.
859
860@item
852A system-call trace of Emacs execution. 861A system-call trace of Emacs execution.
853 862
854System-call traces are very useful for certain special kinds of 863System-call traces are very useful for certain special kinds of