From: Dmitry Neverov via Gdb <gdb@sourceware.org>
To: Dmitry Neverov via Gdb <gdb@sourceware.org>
Subject: Debuginfod in an interactive gdb frontend
Date: Tue, 7 May 2024 10:57:59 +0200 [thread overview]
Message-ID: <CAEY59_LNnDE9gZFkUgOMwZMpm-CGSkK0YOogtw+E4pCu+uHyQQ@mail.gmail.com> (raw)
Please suggest how to integrate with debuginfod in the interactive gdb frontend.
Since loading debug information can be slow, I'd like to ask the user
before loading, similar to what `set debuginfod enabled ask` does in
the terminal. The 'set debuginfod enabled ask' defaults to 'N' in the
non-interactive terminal. Is there any way to hook into this
interaction and make the answer depend on user choice in UI without
typing in the console?
Also since loading takes time, I'd like to show some progress in UI.
Is it possible to get notified when the debuginfo loading for a given
binary starts/finishes, and with which result?
I thought I could write a MissingDebugHandler in python and wrap
debuginfod with necessary progress, but it looks like debuginfod api
is not available in python.
--
Dmitry
next reply other threads:[~2024-05-07 8:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-07 8:57 Dmitry Neverov via Gdb [this message]
2024-05-07 18:48 ` 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=CAEY59_LNnDE9gZFkUgOMwZMpm-CGSkK0YOogtw+E4pCu+uHyQQ@mail.gmail.com \
--to=gdb@sourceware.org \
--cc=dmitry.neverov@jetbrains.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