From: Milian Wolff <mail@milianw.de>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: elfutils-devel@sourceware.org
Subject: Re: Expanding control over debuginfod usage from dwfl [was: Re: Questions regarding debuginfod.h API]
Date: Wed, 06 Jul 2022 21:44:44 +0200 [thread overview]
Message-ID: <4558765.LvFx2qVVIh@agathemoarbauer> (raw)
In-Reply-To: <20220706194133.GE9702@redhat.com>
On Mittwoch, 6. Juli 2022 21:41:33 CEST Frank Ch. Eigler wrote:
> Hi -
>
> > a) Notifying the user that a download is ongoing. Right now, it feels like
> > the tool is frozen as no feedback is given to the user.
>
> Right, can you explain how DEBUGINFOD_PROGRESS=1 is not a good fit in your
> case?
As you said yourself:
> There is a
> DEBUGINFOD_PROGRESS env var with which it can activate some
> notification to stderr, but that's about it.
I'm working on GUI applications (hotspot [1], gammaray [2]), people do not
look at the command line output. I want to show the download progress and
status graphically instead.
[1]: https://github.com/KDAB/hotspot/
[2]: https://github.com/KDAB/gammaray
--
Milian Wolff
http://milianw.de
next prev parent reply other threads:[~2022-07-06 19:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 12:44 Questions regarding debuginfod.h API Milian Wolff
2022-04-08 13:44 ` Frank Ch. Eigler
2022-04-08 19:09 ` Milian Wolff
2022-04-08 19:44 ` Frank Ch. Eigler
2022-04-08 19:50 ` Milian Wolff
2022-04-09 13:44 ` Expanding control over debuginfod usage from dwfl [was: Re: Questions regarding debuginfod.h API] Milian Wolff
2022-07-06 18:28 ` Milian Wolff
2022-07-06 18:40 ` Frank Ch. Eigler
2022-07-06 19:37 ` Milian Wolff
2022-07-06 19:41 ` Frank Ch. Eigler
2022-07-06 19:44 ` Milian Wolff [this message]
2022-07-06 19:54 ` Frank Ch. Eigler
2022-04-16 15:03 ` Questions regarding debuginfod.h API Frank Ch. Eigler
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=4558765.LvFx2qVVIh@agathemoarbauer \
--to=mail@milianw.de \
--cc=elfutils-devel@sourceware.org \
--cc=fche@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).