Re: Semihosting in GDB 11.1 | Proposed patch for interrupting in sync mode

>>>>> Adrian Oltean via Gdb <[email protected]> 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