[Bug gdb/20959] New: New UI errors not propagated to MI console

["marc.khouzam at ericsson dot com" <sourceware-bugzilla at sourceware dot org>]

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

            Bug ID: 20959
           Summary: New UI errors not propagated to MI console
           Product: gdb
           Version: 7.12
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: marc.khouzam at ericsson dot com
                CC: antoine.tremblay at ericsson dot com, palves at redhat dot com,
                    simon.marchi at polymtl dot ca
  Target Milestone: ---

We've run into a scenario where the new UI reports an error to the user but not
on the MI channel; therefore the frontend is not aware of the real state of GDB
because it missed the error.  See below for the scenario:

On the CLI UI:
> gdb.master -ex "new-ui mi /dev/pts/9" testing/a.out
GNU gdb (GDB) 7.12.50.20161212-git
[..]
Reading symbols from testing/a.out...done.
New UI allocated
(gdb) start
Temporary breakpoint 1 at 0x4004b8: file test.cc, line 2.
Starting program: /home/lmckhou/testing/a.out 

Temporary breakpoint 1, main () at test.cc:2
2           int a = 2;
(gdb) b *0
Breakpoint 2 at 0x0
(gdb) c
Continuing.
Warning:
Cannot insert breakpoint 2.
Cannot access memory at address 0x0

Command aborted.
(gdb) i thread
  Id   Target Id         Frame 
* 1    process 28360 "a.out" main () at test.cc:2

On the MI UI (only showing what happens once I type the 'b *0' command in the
CLI:

=breakpoint-created,bkpt={number="2",type="breakpoint",disp="keep",enabled="y",addr="0x0000000000000000",thread-groups=["i1"],times="0",original-location="*0"}
*running,thread-id="all"

Notice that there is no indication for the frontend on the MI channel that
anything bad happened, so the frontend thinks the thread is running.

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