Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: eliz@gnu.org, gdb-patches@sources.redhat.com
Subject: [rfc/doco] bug reporting: mention 'script' command
Date: Thu, 17 Jun 2004 20:52:00 -0000	[thread overview]
Message-ID: <20040617205252.AC4A04B104@berman.michael-chastain.com> (raw)

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


             reply	other threads:[~2004-06-17 20:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-17 20:52 Michael Elizabeth Chastain [this message]
2004-06-18 18:36 ` Eli Zaretskii
2004-06-18 19:55 Michael Elizabeth Chastain
2004-06-19  8:32 ` Eli Zaretskii
2004-06-19 17:28 Michael Elizabeth Chastain

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040617205252.AC4A04B104@berman.michael-chastain.com \
    --to=mec.gnu@mindspring.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox