Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Hui Zhu <teawater@gmail.com>, Tom Tromey <tromey@redhat.com>,
		gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] not trigger pagination with dprintf
Date: Tue, 07 May 2013 17:01:00 -0000	[thread overview]
Message-ID: <CADPb22SD8H0HmopqHY7iFbFE+xFE2X092XgcBXeJ5CNm-W_Rgw@mail.gmail.com> (raw)
In-Reply-To: <83k3naeodd.fsf@gnu.org>

On Tue, May 7, 2013 at 9:38 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Hui Zhu <teawater@gmail.com>
>> Date: Tue, 7 May 2013 10:29:39 +0800
>> Cc: Tom Tromey <tromey@redhat.com>, gdb-patches ml <gdb-patches@sourceware.org>,
>>       Eli Zaretskii <eliz@gnu.org>
>>
>> --- a/gdb/NEWS
>> +++ b/gdb/NEWS
>> @@ -51,6 +51,9 @@ show remote trace-status-packet
>>    ** The -trace-save MI command can optionally save trace buffer in Common
>>       Trace Format now.
>>
>> +* When GDB executes the commands of any breakpoint, the GDB output
>> +  pagination will be auto set to off.
>                         ^^^^
> "automatically"

I would add "... set to off for the duration of the breakpoint commands."
or something like that.

>> --- a/gdb/doc/gdb.texinfo
>> +++ b/gdb/doc/gdb.texinfo
>> @@ -4619,6 +4619,9 @@ commands to execute when your program st
>>  example, you might want to print the values of certain expressions, or
>>  enable other breakpoints.
>>
>> +When @value{GDBN} executes the commands of any breakpoint,
>> +the @value{GDBN} output pagination will be auto set to off.
>                                               ^^^^
> Same here.

nit: I previously mentioned adding a note saying that any change to
pagination done by the user during breakpoint commands is reverted,
but that was left out.

> OK with these changes.
>
> Thanks.

Plus, for reference sake, we still haven't decided to go this route.
I'm kinda on the fence, and I'd like to hear what other GMs think.

[I realize you're just reviewing the doc parts (and thanks for that).]


  reply	other threads:[~2013-05-07 17:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-19  3:22 Hui Zhu
2013-04-20  8:20 ` Tom Tromey
2013-04-22  9:21   ` Hui Zhu
2013-04-25  8:02     ` Tom Tromey
2013-04-26 13:55       ` Hui Zhu
2013-04-26 14:14         ` Yao Qi
2013-04-27 11:40         ` Tom Tromey
2013-04-30 11:12           ` Hui Zhu
2013-05-04  4:41             ` Doug Evans
2013-05-07  2:30               ` Hui Zhu
2013-05-07 16:39                 ` Eli Zaretskii
2013-05-07 17:01                   ` Doug Evans [this message]
2013-05-07 18:08                     ` Tom Tromey
2013-05-07 18:10                       ` Doug Evans
2013-05-07 18:28                         ` Eli Zaretskii
2013-05-10 11:21                           ` Hui Zhu

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=CADPb22SD8H0HmopqHY7iFbFE+xFE2X092XgcBXeJ5CNm-W_Rgw@mail.gmail.com \
    --to=dje@google.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=teawater@gmail.com \
    --cc=tromey@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