This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

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


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

            Bug ID: 20487
           Summary: Thread sync broken between mi and cli with new-ui
                    command
           Product: gdb
           Version: 7.12
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: antoine.tremblay at ericsson dot com
  Target Milestone: ---

Before the new-ui command, one way to interact with GDB's cli while in mi was
to use directly the cli commands in mi or use interpreter-exec.

Using this method doing a cli thread selection using "thread x" generates a
thread-selected event.

E.g: 
(gdb) 
thread 1
&"thread 1\n"
~"[Switching to thread 1 (Thread 0x7ffff7fc7740 (LWP 15517))]\n"
~"#0  0x00007ffff7bc565b in pthread_join () from
/lib/x86_64-linux-gnu/libpthread.so.0\n"
^done
=thread-selected,id="1"

Thus the mi front-end is able to select the proper thread.

If you try the same selection but using a cli created with new-ui you will get
no thread event.

This breaks the sync with the front-end.

I will post a patch soon that fixes this issue soon and also syncs the frame.

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

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]