2004-06-19 Michael Chastain <mec.gnu@mindspring.com>

	gdb.texinfo (Bug Reporting): Mention session recording,
	with the script command or Emacs.

diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index 4f8218e8fff5959f5994c6818c16a126eb06443b..6934004d85f95ae758a1ab5670d55fe7b721d54c 100644 (file)
--- a/gdb/doc/ChangeLog
+++ b/gdb/doc/ChangeLog
@@ -1,3 +1,8 @@
+2004-06-19  Michael Chastain  <mec.gnu@mindspring.com>
+
+       gdb.texinfo (Bug Reporting): Mention session recording,
+       with the script command or Emacs.
+
 2004-06-18  Andrew Cagney  <cagney@gnu.org>
 
        * gdbint.texinfo (Target Architecture Definition): Deprecate

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index e5a6f2e551212d4c2f34d49db970136ebb15ad3e..2ae7472a74c4e8d4d1228fab107635f6a0a5203f 100644 (file)
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -18960,6 +18960,16 @@ ours fails to crash, we would know that the bug was not happening for
 us.  If you had not told us to expect a crash, then we would not be able
 to draw any conclusion from our observations.
 
+@pindex script
+@cindex recording a session script
+To collect all this information, you can use a session recording program
+such as @command{script}, which is available on many Unix systems.
+Just run your @value{GDBN} session inside @command{script} and then
+include the @file{typescript} file with your bug report.
+
+Another way to record a @value{GDBN} session is to run @value{GDBN}
+inside Emacs and then save the entire buffer to a file.
+
 @item
 If you wish to suggest changes to the @value{GDBN} source, send us context
 diffs.  If you even discuss something in the @value{GDBN} source, refer to