From: Tom Tromey <tom@tromey.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: gdb@sourceware.org, qemu-devel@nongnu.org,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
tom@tromey.com, pedro@palves.net
Subject: Re: How to backtrace an separate stack?
Date: Mon, 07 Mar 2022 09:58:54 -0700 [thread overview]
Message-ID: <87mti11yy9.fsf@tromey.com> (raw)
In-Reply-To: <YiCk+NNtAGQPhyK5@stefanha-x1.localdomain> (Stefan Hajnoczi's message of "Thu, 3 Mar 2022 11:22:32 +0000")
>>>>> "Stefan" == Stefan Hajnoczi <stefanha@redhat.com> writes:
Stefan> I hoped that "select-frame address ADDRESS" could be used instead so
Stefan> this would work on coredumps too. Unfortunately "select-frame" only
Stefan> searches stack frames that GDB is already aware of, so it cannot be used
Stefan> to backtrace coroutine stacks.
I wonder if "select-frame view" is closer to what you want.
I can't attest to how well it works or doesn't work. I've never tried
it.
Stefan> Is there a way to backtrace a stack at an arbitrary address in GDB?
IMO this is just a longstanding hole in GDB. Green threads exist, so it
would be good for GDB to have a way to inspect them.
For Ada, this problem was solved by adding knowledge of the runtime to
GDB itself -- that's basically what the "ravenscar" stuff is about. Not
necessarily an approach I'd recommend.
I think the main problem with adding green thread support is just
finding someone to do the work. Personally I think a decent approach
would be to add some core code to handle this, and then expose some
necessary bits via the Python API, so that user programs like qemu could
ship Python code that would replicate the ideas in the ravenscar layer
-- grovelling around in the inferior data structures to find info about
the thread.
Note that some of the GDB work might be complicated. For ravenscar,
there's still an AdaCore-local patch (sent to gdb-patches but not really
suitable for inclusion) to avoid problems with "random thread switches"
-- there were problems where the current thread would, from GDB's
perspective, unexpectedly change when single-stepping through the green
scheduler.
Tom
next prev parent reply other threads:[~2022-03-07 16:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 11:22 Stefan Hajnoczi
2022-03-07 10:49 ` Pedro Alves
2022-03-08 9:47 ` Stefan Hajnoczi
2022-03-07 14:49 ` Florian Weimer
2022-03-07 17:30 ` Tom Tromey
2022-03-09 10:06 ` Florian Weimer
2022-03-09 19:50 ` Tom Tromey
2022-03-07 16:58 ` Tom Tromey [this message]
2022-03-07 17:18 ` Pedro Alves
2022-03-08 8:43 ` Stefan Hajnoczi
2022-03-14 20:30 ` Tom Tromey
2022-03-15 14:17 ` Stefan Hajnoczi
2022-03-18 21:13 ` 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=87mti11yy9.fsf@tromey.com \
--to=tom@tromey.com \
--cc=dgilbert@redhat.com \
--cc=gdb@sourceware.org \
--cc=pedro@palves.net \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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).