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

["antoine.tremblay at ericsson dot com" <sourceware-bugzilla at sourceware dot org>]

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

--- Comment #3 from Antoine Tremblay <antoine.tremblay at ericsson dot com> ---
Pedro:

Ooops I made a mistake in my description I meant if you do the same with mi
created with new-ui like so :

(gdb) new mi /dev/pts/0
New UI allocated
(gdb) break 33
Breakpoint 1 at 0x4007b4: file ./thread-selected-sync.c, line 33.
(gdb) r
Starting program: /home/eantotr/src/test-thread-selected/test 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffff77f6700 (LWP 24810)]
[New Thread 0x7ffff6ff5700 (LWP 24811)]
[Switching to Thread 0x7ffff6ff5700 (LWP 24811)]

Thread 3 "test" hit Breakpoint 1, child_sub_function () at
./thread-selected-sync.c:33
33        while (!quit) /* set break here */
(gdb) thread 2
[Switching to thread 2 (Thread 0x7ffff77f6700 (LWP 24810))]
#0  child_sub_function () at ./thread-selected-sync.c:33
33        while (!quit) /* set break here */
(gdb) 

Then you don't get an MI event.

My solution at the moment is to do fire an event in gdb_thread_select...

Even if I get into some little trouble with safe_execute_command.

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