This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [rfc/doco] bug reporting: mention 'script' command


Okay, here's draft #2.  I mentioned Emacs as well as 'script'.
I added a @pindex and a @cindex.

Testing: Rebuilt gdb.info and checked the output files.

Okay to commit?

Michael C

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

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

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	18 Jun 2004 19:51:25 -0000
*************** ours fails to crash, we would know that 
*** 18960,18965 ****
--- 18960,18975 ----
  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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]