Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Tom Tromey (Code Review)" <gerrit@gnutoolchain-gerrit.osci.io>
To: Luis Machado <luis.machado@linaro.org>, gdb-patches@sourceware.org
Subject: [review v2] [Debugging output] Make remote packet truncation length adjustable
Date: Thu, 21 Nov 2019 14:41:00 -0000	[thread overview]
Message-ID: <20191121144103.BB8F42816F@gnutoolchain-gerrit.osci.io> (raw)
In-Reply-To: <gerrit.1574263562000.I2e871b37bfcaa6376537c3fe3db8f016dd806a7c@gnutoolchain-gerrit.osci.io>

Tom Tromey has posted comments on this change.

Change URL: https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/691
......................................................................


Patch Set 2: Code-Review+1

(1 comment)

Thank you.  I have a small suggestion for the docs, but otherwise
everything looks good.

I'm marking this +1 since Eli should review the doc changes.

| --- gdb/doc/gdb.texinfo
| +++ gdb/doc/gdb.texinfo
| @@ -26273,7 +26273,20 @@ the serial line to the remote machine.  The info is printed on the
|  @value{GDBN} standard output stream. The default is off.
|  @item show debug remote
|  Displays the state of display of remote packets.
|  
| +@item set debug remote-log-length
| +Sets the number of characters to display for each remote packet when
| +@code{set debug remote} is on. This is useful to prevent GDB from
| +displaying lengthy remote packets and polluting the console.
| +
| +The default value is @code{512}, which means @value{GDBN} will truncate the
| +remote packet output after 512 bytes.

PS2, Line 26283:

I think maybe this should say something like "will truncate each
remote packet after 512 bytes" ... the current text makes it sound
a bit like the entirety of the output will be truncated.

| +
| +Setting this option to @code{unlimited} will disable truncation and will output
| +the full length of the remote packets.
| +@item show debug remote-log-length
| +Displays the number of bytes to output for remote packet debugging.
| +
|  @item set debug separate-debug-file
|  Turns on or off display of debug output about separate debug file search.
|  @item show debug separate-debug-file

-- 
Gerrit-Project: binutils-gdb
Gerrit-Branch: master
Gerrit-Change-Id: I2e871b37bfcaa6376537c3fe3db8f016dd806a7c
Gerrit-Change-Number: 691
Gerrit-PatchSet: 2
Gerrit-Owner: Luis Machado <luis.machado@linaro.org>
Gerrit-Reviewer: Luis Machado <luis.machado@linaro.org>
Gerrit-Reviewer: Tom Tromey <tromey@sourceware.org>
Gerrit-Comment-Date: Thu, 21 Nov 2019 14:41:02 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: Yes
Gerrit-MessageType: comment


  parent reply	other threads:[~2019-11-21 14:41 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-20 15:26 [review] " Luis Machado (Code Review)
2019-11-20 15:27 ` Luis Machado (Code Review)
2019-11-20 18:12 ` Tom Tromey (Code Review)
2019-11-20 18:42 ` Luis Machado (Code Review)
2019-11-20 20:35 ` [review v2] " Luis Machado (Code Review)
2019-11-21 15:05   ` Eli Zaretskii
2019-11-21 14:41 ` Tom Tromey (Code Review) [this message]
2019-11-21 15:17 ` [review v3] " Luis Machado (Code Review)
2019-11-21 15:25   ` Eli Zaretskii
2019-11-21 16:31 ` Pedro Alves (Code Review)
2019-11-21 17:15 ` [review v4] " Luis Machado (Code Review)
2019-11-21 18:55 ` Pedro Alves (Code Review)
2019-11-21 21:49 ` Luis Machado (Code Review)
2019-11-21 21:49 ` Luis Machado (Code Review)
2019-11-21 22:03 ` [review v5] " Luis Machado (Code Review)
2019-11-22  7:34   ` Eli Zaretskii
2019-11-22 15:22 ` Pedro Alves (Code Review)
2019-11-25 13:31 ` [review v6] " Luis Machado (Code Review)
2019-11-25 15:34   ` Eli Zaretskii
2019-11-25 13:33 ` Luis Machado (Code Review)
2019-11-25 15:30 ` [pushed] " Sourceware to Gerrit sync (Code Review)
2019-11-25 15:30 ` Sourceware to Gerrit sync (Code Review)

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=20191121144103.BB8F42816F@gnutoolchain-gerrit.osci.io \
    --to=gerrit@gnutoolchain-gerrit.osci.io \
    --cc=gdb-patches@sourceware.org \
    --cc=gnutoolchain-gerrit@osci.io \
    --cc=luis.machado@linaro.org \
    /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