This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
[rfc/doco] bug reporting: mention 'script' command
- From: mec dot gnu at mindspring dot com (Michael Elizabeth Chastain)
- To: eliz at gnu dot org, gdb-patches at sources dot redhat dot com
- Date: Thu, 17 Jun 2004 16:52:52 -0400 (EDT)
- Subject: [rfc/doco] bug reporting: mention 'script' command
Here's a bit of doco which mentions the 'script' command for bug reporting.
I've been wanting to do this for a while.
Testing: I rebuilt gdb to make sure the texinfo syntax is okay.
Comments on the syntax?
Comments on the content?
Michael C
2004-06-17 Michael Chastain <mec.gnu@mindspring.com>
gdb.texinfo (Bug Reporting): Mention the script command.
Index: gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.206
diff -c -3 -p -r1.206 gdb.texinfo
*** gdb.texinfo 14 Jun 2004 22:26:33 -0000 1.206
--- gdb.texinfo 17 Jun 2004 20:40:23 -0000
*************** ours fails to crash, we would know that
*** 18960,18965 ****
--- 18960,18970 ----
us. If you had not told us to expect a crash, then we would not be able
to draw any conclusion from our observations.
+ 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.
+
@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