This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] not trigger pagination with dprintf
- From: Hui Zhu <teawater at gmail dot com>
- To: Tom Tromey <tromey at redhat dot com>
- Cc: gdb-patches ml <gdb-patches at sourceware dot org>
- Date: Fri, 26 Apr 2013 11:35:02 +0800
- Subject: Re: [PATCH] not trigger pagination with dprintf
- References: <CANFwon2V2vVADH89czoQjS+F=Uxsc5AgMAsQ3=d0nohc2EfBpA at mail dot gmail dot com> <87zjwuv0qn dot fsf at fleche dot redhat dot com> <CANFwon1kWpR9mhGVbzf0qB4GqO89yN+Uj9jGUHpp2-kWWmFC4g at mail dot gmail dot com> <87li87ll0r dot fsf at fleche dot redhat dot com>
On Thu, Apr 25, 2013 at 4:40 AM, Tom Tromey <tromey@redhat.com> wrote:
>>>>>> "Hui" == Hui Zhu <teawater@gmail.com> writes:
>
> Hui> Will you OK if I update patch to make printf_command call ui_printf
> Hui> with filter is 0 just with dprintf?
>
> I just don't understand why dprintf should be special in this regard.
> Nothing else is.
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.
Thanks,
Hui
>
> Tom