From: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
To: "Martin Liška" <mliska@suse.cz>, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: print size of downloaded debuginfod binary
Date: Mon, 7 Dec 2020 12:07:12 -0500 [thread overview]
Message-ID: <c89c3c7a-e17f-63ea-b32d-3b9132a7cf2e@polymtl.ca> (raw)
In-Reply-To: <6ad82f30-0ca3-8b19-2907-d71f0dfecafe@suse.cz>
On 2020-12-07 6:43 a.m., Martin Liška wrote:
> With the patch, one can see now:
>
> Reading symbols from /usr/bin/gcc...
> Downloading 2.69 MiB separate debug info for /usr/bin/gcc...
> Downloading 1.00 MiB separate debug info for /lib64/ld-linux-x86-64.so.2...
> Downloading 10.72 MiB separate debug info for /lib64/libc.so.6...
> ...
I think that's a good idea. Given that we don't have a progress bar
(yet), this gives clue to the user about why it might take some time.
Let's see if others have other opinions about this. If nothing comes
for by next week, you can go ahead and merge it.
Simon
next prev parent reply other threads:[~2020-12-07 17:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-07 11:43 Martin Liška
2020-12-07 17:07 ` Simon Marchi via Gdb-patches [this message]
2020-12-08 10:16 ` Martin Liška
2020-12-08 14:28 ` Simon Marchi via Gdb-patches
2020-12-09 10:51 ` Martin Liška
2020-12-09 23:26 ` Tom de Vries
2020-12-10 8:26 ` Martin Liška
2020-12-10 19:21 ` Tom Tromey
2020-12-11 17:51 ` [gdb/cli] Add a progress meter Tom de Vries
2020-12-11 17:54 ` [PATCH] gdb: print size of downloaded debuginfod binary Tom de Vries
2020-12-11 19:23 ` Tom Tromey
2020-12-12 16:43 ` Tom de Vries
2020-12-15 20:29 ` Tom Tromey
2020-12-11 19:21 ` [gdb/cli] Add a progress meter Tom Tromey
2020-12-12 16:35 ` Tom de Vries
2020-12-15 20:28 ` Tom Tromey
2020-12-09 20:16 ` [PATCH] gdb: print size of downloaded debuginfod binary 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=c89c3c7a-e17f-63ea-b32d-3b9132a7cf2e@polymtl.ca \
--to=gdb-patches@sourceware.org \
--cc=mliska@suse.cz \
--cc=simon.marchi@polymtl.ca \
/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