From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
To: Tom Tromey <tom@tromey.com>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sourceware.org
Subject: Re: Still some style problems with 8.3 branch
Date: Thu, 11 Apr 2019 21:02:00 -0000 [thread overview]
Message-ID: <1555016515.1446.10.camel@skynet.be> (raw)
In-Reply-To: <874l748i1d.fsf@tromey.com>
On Thu, 2019-04-11 at 13:21 -0600, Tom Tromey wrote:
> > > > > > "Philippe" == Philippe Waroquiers <philippe.waroquiers@skynet.be> writes:
>
> Philippe> It works better with the patch, but even with the patch,
> Philippe> I still encountered one case where the style was not
> Philippe> the expected style after the continuation prompt.
>
> I tried this and couldn't reproduce, but...
>
> Philippe> To reproduce (in a 80x24 terminal):
> Philippe> ./gdb/gdb ./gdb/gdb
> Philippe> break cli_ui_out::do_field_string
> Philippe> run
> gdb/testsuite/outputs/gdb.ada/info_auto_lang/proc_in_ada
> Philippe> Â (gdb) b proc_in_c
> Philippe> Â (gdb) run
> Philippe> info func error
> Philippe> #### then type several times return at the page prompt.
> Philippe> #### At some point in time, you see
>
> ...I may not fully understand the instructions - the breakpoint on
> do_field_string seems to interfere with getting paging to work in the
> inferior gdb.
Maybe what is unclear is what to give to the top-gdb, and what to
give to the inferior gdb.
You should be able to reproduce it by just
typing one after each other the following lines.
I have put before the info to type which process is getting the input:
shell: ./gdb/gdb ./gdb/gdb
top-gdb: break cli_ui_out::do_field_string
top-gdb: run gdb/testsuite/outputs/gdb.ada/info_auto_lang/proc_in_ada
gdb: b proc_in_c
gdb: run
top-gdb: info func error
.... and then a bunch of return, till an output line is wrongly styled
in black, just after a prompt for continue.
Philippe
next prev parent reply other threads:[~2019-04-11 21:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-30 10:36 Philippe Waroquiers
2019-03-31 14:28 ` Eli Zaretskii
2019-04-03 18:21 ` Eli Zaretskii
2019-04-03 20:07 ` Tom Tromey
2019-04-07 10:08 ` Philippe Waroquiers
2019-04-11 19:21 ` Tom Tromey
2019-04-11 21:02 ` Philippe Waroquiers [this message]
2019-04-11 19:20 ` Tom Tromey
2019-04-12 12:39 ` Eli Zaretskii
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=1555016515.1446.10.camel@skynet.be \
--to=philippe.waroquiers@skynet.be \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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