From: Eli Zaretskii <eliz@gnu.org>
To: Hui Zhu <teawater@gmail.com>
Cc: dje@google.com, tromey@redhat.com, gdb-patches@sourceware.org
Subject: Re: [PATCH] not trigger pagination with dprintf
Date: Tue, 07 May 2013 16:39:00 -0000 [thread overview]
Message-ID: <83k3naeodd.fsf@gnu.org> (raw)
In-Reply-To: <CANFwon3HJye8SdLL8jV8H7-g-BipNON6+oS2p8J=QpnnrXbdFA@mail.gmail.com>
> 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"
> --- 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.
OK with these changes.
Thanks.
next prev parent reply other threads:[~2013-05-07 16:39 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 [this message]
2013-05-07 17:01 ` Doug Evans
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=83k3naeodd.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dje@google.com \
--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