From: "Denio, Mike" <miked@ti.com>
To: Pedro Alves <pedro@palves.net>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: RE: [EXTERNAL] Re: RiscV GDB remote protocol seems to expect stop reply to change Hg in all-stop mode
Date: Fri, 8 Apr 2022 21:56:23 +0000 [thread overview]
Message-ID: <78473f635612487bb0d0619042486d7c@ti.com> (raw)
In-Reply-To: <12dff0f1-86cf-6e73-e0bb-0e6a09ab5f83@palves.net>
Thanks for the info. Its not big deal as It's something that becomes obvious with use. I just thought I'd mention it.
I misspoke in my last e-mail. I forgot that I actually ignore the Hc command now and base everything on the vCont.
If you have any thoughts on my other message, please let me know. For now, I'm going to rely on the 'T' command in all-stop mode to know that GDB has changed the current thread, but it would be nice if there was an official method.
Mike
-----Original Message-----
From: Pedro Alves <pedro@palves.net>
Sent: Friday, April 08, 2022 4:41 PM
I could swear this was documented, but I can't actually find it either. This has "always" been this way, AFAIK.
[...]
GDB only auto-changes the Hg thread, see record_currthread.
prev parent reply other threads:[~2022-04-08 21:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 15:36 Denio, Mike
2022-04-08 21:41 ` Pedro Alves
2022-04-08 21:56 ` Denio, Mike [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=78473f635612487bb0d0619042486d7c@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).