public inbox for
 help / color / mirror / Atom feed
From: Tom Tromey <>
To: Adrian Oltean via Gdb <>
Cc: Adrian Oltean <>
Subject: Re: Semihosting in GDB 11.1 | Proposed patch for interrupting in sync mode
Date: Tue, 08 Mar 2022 15:10:14 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> (Adrian Oltean via Gdb's message of "Mon, 7 Mar 2022 19:39:40 +0000")

>>>>> Adrian Oltean via Gdb <> 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


  reply	other threads:[~2022-03-08 22:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-07 19:39 Adrian Oltean
2022-03-08 22:10 ` Tom Tromey [this message]
2022-03-09  7:25 Adrian Oltean
2022-03-09 19:49 ` Tom Tromey
2022-03-10  9:47   ` Pedro Alves

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).