From: Pedro Alves <pedro@palves.net>
To: "Denio, Mike" <miked@ti.com>, "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: [EXTERNAL] Re: Issue with multiple threads using remote protocol on riscv32
Date: Thu, 17 Mar 2022 17:52:06 +0000 [thread overview]
Message-ID: <614d4e0d-98ae-f507-f1ff-aca0e94a483a@palves.net> (raw)
In-Reply-To: <cda38d5f44d442f8ab282a21fb8ace2e@ti.com>
On 2022-03-16 15:10, Denio, Mike wrote:
> Ok, thanks. I'll have to think about how I'm going to implement that.
>
> Is it safe to assume that this only affects the initial event, and that once I see the first 'vStopped', GDB will not interlace more 'vCont' commands?
>
> For example, say I had 8 newly stopped threads such that GDB will end up calling 'vStopped' 8 times. Is it safe to assume that GDB will not send any new vCont in the middle of sending those 8 vStopped?
Currently, when GDB issues a vStopped, it keeps issuing it until the remote side returns OK, indicating no more pending events.
But I wouldn't trust that that won't ever change. Imagine at some point we come to the conclusion that it would be better to
batch fetching pending events, so that GDB went on to process the pending events once it fetches some N events out of vStopped,
maybe go on to process events out of some other remote connection / target, and then goes back to fetching another batch
of N events out of the first remote connection, and so forth.
next prev parent reply other threads:[~2022-03-17 17:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-16 14:45 Denio, Mike
2022-03-16 14:58 ` Pedro Alves
2022-03-16 15:10 ` [EXTERNAL] " Denio, Mike
2022-03-17 17:52 ` Pedro Alves [this message]
2022-03-17 19:11 ` Denio, Mike
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=614d4e0d-98ae-f507-f1ff-aca0e94a483a@palves.net \
--to=pedro@palves.net \
--cc=gdb@sourceware.org \
--cc=miked@ti.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).