[Bug gdb/20487] Thread sync broken between mi and cli with new-ui command

["simon.marchi at ericsson dot com" <sourceware-bugzilla at sourceware dot org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=20487

--- Comment #11 from Simon Marchi <simon.marchi at ericsson dot com> ---
(In reply to Pedro Alves from comment #5)
> This sounds an awful lot like what Simon was handling around MI's --thread
> option.
> 
> I mean, it's not just the "thread" command that changes current thread.  We
> have at least "inferior", and "run&", "attach&", "core", and probably others.


Right, when we implement your suggestion (decouple user selection from gdb's
internal selection), emitting the =thread-selected notification should be easy,
as it will be clear when the user selection changes.  There will be one or two
functions responsible for modifying the user selection, so the event should be
sent from there.

-- 
You are receiving this mail because:
You are on the CC list for the bug.