From: Tom Tromey <tom@tromey.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: Tom Tromey <tom@tromey.com>,
gdb@sourceware.org, qemu-devel@nongnu.org, pedro@palves.net,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: How to backtrace an separate stack?
Date: Fri, 18 Mar 2022 15:13:08 -0600 [thread overview]
Message-ID: <87ee2zezh7.fsf@tromey.com> (raw)
In-Reply-To: <YjCf8BPW+jITJain@stefanha-x1.localdomain> (Stefan Hajnoczi's message of "Tue, 15 Mar 2022 14:17:20 +0000")
>> You can play with this if you want. It's on 'submit/green-threads' on
>> my github. Be warned that I rebase a lot.
Stefan> This looks cool! Would it be useful to see a port of QEMU's coroutine.py
Stefan> script to your green threads API?
Wouldn't hurt :)
Stefan> QEMU's coroutines aren't in a scheduler list so there is no way to
Stefan> enumerate all coroutines. The Python script can register a GDB command
Stefan> (e.g. "qemu coroutine 0x12345678") that makes GDB aware of the
Stefan> coroutine.
On the one hand, maybe this means the model is wrong.
On the other, I suppose qemu could also have a new command to create a
temporary "thread", given a ucontext_t (or whatever), and switch to it.
Then when the user "continue"s, the thread could be deleted again.
Tom
prev parent reply other threads:[~2022-03-18 21:13 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
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 [this message]
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=87ee2zezh7.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).