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: Tue, 8 Dec 2020 09:28:12 -0500 [thread overview]
Message-ID: <cfcaa2c3-0708-d2f5-ba8d-18d7e28954ca@polymtl.ca> (raw)
In-Reply-To: <2c28a403-a169-0dc3-9b64-58484237c8c2@suse.cz>
On 2020-12-08 5:16 a.m., Martin Liška wrote:
> Temporary breakpoint 1 at 0x406150: file
> /home/marxin/Programming/gcc/gcc/gcc-main.c, line 44.
> Starting program: /home/marxin/bin/gcc/bin/gcc
> Downloading 1.00 MB separate debug info for
> /lib64/ld-linux-x86-64.so.2...10%..20%..30%..40%..50%..60%..70%..80%..90%..100%
>
> Downloading 4.20 MB separate debug info for
> /lib64/libm.so.6...10%..20%..30%..40%..50%..60%..70%..80%..90%..100%
> Downloading 10.72 MB separate debug info for
> /lib64/libc.so.6...10%..20%..30%..40%..50%
>
> Thoughts?
Could you make it so the percentage always gets written at the same
place, overwriting the previous percentage written?
Simon
next prev parent reply other threads:[~2020-12-08 14:28 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
2020-12-08 10:16 ` Martin Liška
2020-12-08 14:28 ` Simon Marchi via Gdb-patches [this message]
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=cfcaa2c3-0708-d2f5-ba8d-18d7e28954ca@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