From: Simon Marchi <simon.marchi@polymtl.ca>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org, Tom Tromey <tromey@redhat.com>
Subject: Re: [RFA 2/2] PR cli/19551 - change formatting of "Reading symbols" messages
Date: Thu, 27 Apr 2017 21:40:00 -0000 [thread overview]
Message-ID: <c5751eb6ffcf4efbe1a5cf38d7127657@polymtl.ca> (raw)
In-Reply-To: <20170413041504.14435-3-tom@tromey.com>
On 2017-04-13 00:15, Tom Tromey wrote:
> From: Tom Tromey <tromey@redhat.com>
>
> PR cli/19551 notes that the "Reading symbols" messages can be messy,
> for
> example:
>
> (gdb) file /bin/gdb
> Reading symbols from /bin/gdb...Reading symbols from /bin/gdb...(no
> debugging symbols found)...done.
> (no debugging symbols found)...done.
>
> In this case the first message is being interrupted by the message for
> the minidebug info; then the subsequent output is emitted strangely.
>
> This patch changes gdb to use a progress bar when reading debug info.
> It modifies the DWARF reader(s) to update the progress. Any printing
> is deferred until the first progress report, so the messages no longer
> clash.
>
> While printing the status message it looks like:
>
> Reading symbols from ./gdb
> [############## ]
>
> The "#"s show the progress; these are only printed on a terminal.
>
> When it is finished it looks like:
>
> Reading symbols from .gnu_debugdata for /usr/bin/gdb
> Reading symbols from /bin/gdb
>
> I made the MI implementation do nothing. MI has a
> "status-async-output" production in the grammar:
>
> 'STATUS-ASYNC-OUTPUT ==>'
> '[ TOKEN ] "+" ASYNC-OUTPUT NL'
>
> ... which maybe could be used for this sort of thing. Currently I
> think
> it's only used for "load" progress (see mi_load_progress); so it wasn't
> clear to me whether this would be a good idea.
Hi Tom,
I think that having a progress bar would be really awesome (right after
making GDB load debug info faster so fast that we don't need one).
However, I think that feature would deserve a patch of its own with a
more expressive title. I am sure many people will be interested, but
like this it's hidden under some obscure bug fix.
Would it be possible to make this patch a simple bug fix and put the
progress bar in a patch of its own?
Thanks,
Simon
next prev parent reply other threads:[~2017-04-27 21:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-13 4:17 [RFA 0/2] Fix PR cli/19551 Tom Tromey
2017-04-13 4:17 ` [RFA 2/2] PR cli/19551 - change formatting of "Reading symbols" messages Tom Tromey
2017-04-18 17:43 ` Pedro Alves
2017-04-18 17:44 ` Pedro Alves
2017-04-20 0:11 ` Tom Tromey
2017-04-27 21:40 ` Simon Marchi [this message]
2017-04-27 23:16 ` Tom Tromey
2017-04-27 23:53 ` Simon Marchi
2017-05-29 17:24 ` Tom Tromey
2017-04-13 4:44 ` [RFA 1/2] Use a distinguishing name for minidebug objfile Tom Tromey
2017-04-18 17:42 ` Pedro Alves
2017-04-19 3:11 ` Tom Tromey
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=c5751eb6ffcf4efbe1a5cf38d7127657@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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