From: Simon Marchi <simark@simark.ca>
To: Aaron Merey <amerey@redhat.com>, gdb-patches@sourceware.org
Cc: Tom Tromey <tom@tromey.com>
Subject: Re: [PATCH v4] Add debuginfod support to GDB
Date: Fri, 21 Feb 2020 20:12:00 -0000 [thread overview]
Message-ID: <1282d65e-5c1c-a7d8-b29d-24dd8036ae2d@simark.ca> (raw)
In-Reply-To: <CAJDtP-QYSMoOmpTU5xXb+fJosS7mG8dMezwYkrwgHw5jN-O9bA@mail.gmail.com>
On 2020-02-20 8:57 p.m., Aaron Merey wrote:
> Hello,
>
> In this iteration of the patch I've modified the debuginfod
> progress function so that it does not preserve the value
> of quit_flag when the user enters ctrl+c. Progress
> updates now print the completion percentage of the
> download. Additional help text is also printed before and
> after a query which provides context for what file is being
> searched for and whether the download was successful.
>
> On IRC we discussed changing the behavior of ctrl+c
> during a download depending on whether an inferior
> is running. This change will come in a future patch at
> some point before the next release.
>
> Aaron
>
I'll have to build debuginfod and configure it, so I can give it a try
and see how it files.
In the mean time: if we fail to parse the server's response as a bfd or
if the build id doesn't match, I think we need to display a warning,
because it probably means that the server sent us something bad, or there
was some problem somewhere in the pipeline.
Currently, if that happens, the user would see "Download successful", but
no debug info loaded, so it's a bit misleading.
Simon
next prev parent reply other threads:[~2020-02-21 20:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 1:58 Aaron Merey
2020-02-21 20:12 ` Simon Marchi [this message]
2020-02-24 4:43 ` Aaron Merey
2020-02-24 20:39 ` Simon Marchi
2020-02-24 20:46 ` Aaron Merey
2020-02-24 20:49 ` Simon Marchi
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=1282d65e-5c1c-a7d8-b29d-24dd8036ae2d@simark.ca \
--to=simark@simark.ca \
--cc=amerey@redhat.com \
--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