From: Tom Tromey <tom@tromey.com>
To: Adrian Oltean <adrian.oltean@nxp.com>
Cc: Tom Tromey <tom@tromey.com>, Adrian Oltean via Gdb <gdb@sourceware.org>
Subject: Re: Semihosting in GDB 11.1 | Proposed patch for interrupting in sync mode
Date: Wed, 09 Mar 2022 12:49:15 -0700 [thread overview]
Message-ID: <87k0d2gb44.fsf@tromey.com> (raw)
In-Reply-To: <VI1PR0402MB286377D8A18B417D40219F3FF10A9@VI1PR0402MB2863.eurprd04.prod.outlook.com> (Adrian Oltean's message of "Wed, 9 Mar 2022 07:25:36 +0000")
Adrian> Unfortunately, I could not find ways to adapt all the other components I have around GDB to
Adrian> work with target-async mode enabled. It is what it is...
I'm a little lost about this, because my mental model is that target
async shouldn't really change anything. I think it is just an
implementation detail about where gdb waits for events -- is it in
wait() or in select()?
So, it would be interesting to learn what the differences are. Perhaps
this can be patched up.
Adrian> Regarding the 'H' packet, I had a second look in the RSP specs
Adrian> where it's stated that '0' indicates an arbitrary
Adrian> process/thread. So, as you mentioned, I changed the GDB server
Adrian> code to simply ensure there's a valid thread stopped marked as
Adrian> 'current'. The original implementation incorrectly assimilated
Adrian> '0' with 'first thread' (always).
I'm a little surprised this matters as well, but anyway I think it's
fine to submit a patch like this. Maybe others have some idea of what's
going on.
Tom
next prev parent reply other threads:[~2022-03-09 19:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 7:25 Adrian Oltean
2022-03-09 19:49 ` Tom Tromey [this message]
2022-03-10 9:47 ` Pedro Alves
2022-03-10 10:02 ` [EXT] " Adrian Oltean
2022-03-10 11:30 ` Pedro Alves
2022-03-10 12:32 ` Pedro Alves
2022-03-14 7:33 ` Adrian Oltean
2022-03-17 17:48 ` Pedro Alves
-- strict thread matches above, loose matches on Subject: below --
2022-03-07 19:39 Adrian Oltean
2022-03-08 22:10 ` 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=87k0d2gb44.fsf@tromey.com \
--to=tom@tromey.com \
--cc=adrian.oltean@nxp.com \
--cc=gdb@sourceware.org \
/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).