From: Adrian Oltean <adrian.oltean@nxp.com>
To: 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, 9 Mar 2022 07:25:36 +0000 [thread overview]
Message-ID: <VI1PR0402MB286377D8A18B417D40219F3FF10A9@VI1PR0402MB2863.eurprd04.prod.outlook.com> (raw)
Hi Tom,
Unfortunately, I could not find ways to adapt all the other components I have around GDB to
work with target-async mode enabled. It is what it is...
Regarding the 'H' packet, I had a second look in the RSP specs where it's stated that '0' indicates
an arbitrary process/thread. So, as you mentioned, I changed the GDB server code to simply
ensure there's a valid thread stopped marked as 'current'. The original implementation incorrectly
assimilated '0' with 'first thread' (always).
Thank you,
Adrian
-----Original Message-----
From: Tom Tromey <tom@tromey.com>
Sent: Wednesday, March 9, 2022 12:10 AM
To: Adrian Oltean via Gdb <gdb@sourceware.org>
Cc: Adrian Oltean <adrian.oltean@nxp.com>
Subject: [EXT] Re: Semihosting in GDB 11.1 | Proposed patch for interrupting in sync mode
Caution: EXT Email
>>>>> Adrian Oltean via Gdb <gdb@sourceware.org> writes:
> 1. I need to run GDB client in all-stop mode with target-async set to off.
> This seems to be a must in order to make some python scripts
> (containing
> gdb.post_event('continue')) interact correctly with Eclipse CDT and
> with some automation I have around the python scripts.
I think it would be better on the whole to figure out a way to make this work with target-async. In the long run I'd prefer that gdb remove sync target wait entirely -- that the default be target-async everywhere.
> but I'd like to know if there's any chance I'll break any use case
> with these changes.
I don't have the answer to that I'm afraid.
> Is the described behavior a known issue inside GDB? Or do I have to
> change something in the server to correct the described behavior?
> [remote] Sending packet: $Hg0#df
I think this request means to switch to any thread for subsequent non-continue/step requests. So, ignoring it is almost the right thing to do, I think the idea is just to ensure that some stopped thread is selected.
Tom
next reply other threads:[~2022-03-09 7:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 7:25 Adrian Oltean [this message]
2022-03-09 19:49 ` Tom Tromey
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=VI1PR0402MB286377D8A18B417D40219F3FF10A9@VI1PR0402MB2863.eurprd04.prod.outlook.com \
--to=adrian.oltean@nxp.com \
--cc=gdb@sourceware.org \
--cc=tom@tromey.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).