public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: "Denio, Mike" <miked@ti.com>
To: Pedro Alves <pedro@palves.net>,
	"gdb@sourceware.org" <gdb@sourceware.org>
Subject: RE: [EXTERNAL] Re: Issue with multiple threads using remote protocol on riscv32
Date: Wed, 16 Mar 2022 15:10:12 +0000	[thread overview]
Message-ID: <cda38d5f44d442f8ab282a21fb8ace2e@ti.com> (raw)
In-Reply-To: <4f443800-59d7-5e87-f89e-b2d574ed071a@palves.net>

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?

Thanks again,
Mike






  reply	other threads:[~2022-03-16 15:10 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   ` Denio, Mike [this message]
2022-03-17 17:52     ` [EXTERNAL] " Pedro Alves
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=cda38d5f44d442f8ab282a21fb8ace2e@ti.com \
    --to=miked@ti.com \
    --cc=gdb@sourceware.org \
    --cc=pedro@palves.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).