Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <yao@codesourcery.com>
To: Hui Zhu <teawater@gmail.com>
Cc: Tom Tromey <tromey@redhat.com>,
	gdb-patches ml	<gdb-patches@sourceware.org>
Subject: Re: [PATCH] not trigger pagination with dprintf
Date: Fri, 26 Apr 2013 14:14:00 -0000	[thread overview]
Message-ID: <517A1DC7.2020703@codesourcery.com> (raw)
In-Reply-To: <CANFwon2jNppHObCEac=aSU6Uq6KLaoC5PGS8Vi3LawA+xzOJ=A@mail.gmail.com>

On 04/26/2013 11:35 AM, Hui Zhu wrote:
> Because as the Marc said in bugzilla, when pagination is triggered,
> inferior execution will be interrupted until the user answers the
> pagination prompt.
> And dptintf breakpoint call printf in its commands.  So I want to make
> dprintf can handle it.

Instead of fixing this problem, could we document that user has to 
disable pagination when dprintf breakpoint is used?  Something similar 
is documented for non-stop here 
<http://sourceware.org/gdb/onlinedocs/gdb/Non_002dStop-Mode.html>

      # If using the CLI, pagination breaks non-stop.
      set pagination off
-- 
Yao (齐尧)


  reply	other threads:[~2013-04-26  6:25 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 [this message]
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
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=517A1DC7.2020703@codesourcery.com \
    --to=yao@codesourcery.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