From: Christian Biesinger <cbiesinger@google.com>
To: Michael Woerister <michaelwoerister@posteo.net>
Cc: Reuben Thomas via Gdb <gdb@sourceware.org>
Subject: Re: Executing code if debuggee is a crash dump?
Date: Tue, 24 Aug 2021 12:09:22 -0400 [thread overview]
Message-ID: <CAPTJ0XHqvXvC8wCDc=4Gs6xiKAthkkS_YOo6eTrMMB6N921RFg@mail.gmail.com> (raw)
In-Reply-To: <e0b2f159b26a4d53b4d01bcbddbcd755@posteo.de>
On Tue, Aug 24, 2021 at 6:08 AM Michael Woerister via Gdb
<gdb@sourceware.org> wrote:
> I'm looking into implementing debugger extensions that help with
> debugging crash dumps of "async" Rust executables. Such an extension
> would need to inspect the complex internals of several async runtime
> implementations. We could potentially make the extension more robust and
> easier to maintain if we provided a standardized inspection API in the
> various runtimes and have the debugger interact with that. The functions
> behind this API would be restricted to not interact with the environment
> (e.g. not allocate memory, etc).
>
> However, my research so far indicates that neither GDB nor any other
> debugger is capable of executing code in a crash dump. Is that true or
> am I overlooking something?
> Would anybody here be able give me a definite answer to this question?
If you can reproduce the bug, you could run under
https://rr-project.org/, which would allow you to call functions.
Christian
next prev parent reply other threads:[~2021-08-24 16:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-24 10:07 Michael Woerister
2021-08-24 13:50 ` Simon Marchi
2021-08-25 8:56 ` Michael Woerister
2021-08-24 16:09 ` Christian Biesinger [this message]
2021-08-25 9:02 ` Michael Woerister
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='CAPTJ0XHqvXvC8wCDc=4Gs6xiKAthkkS_YOo6eTrMMB6N921RFg@mail.gmail.com' \
--to=cbiesinger@google.com \
--cc=gdb@sourceware.org \
--cc=michaelwoerister@posteo.net \
/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).