gdb 7.11 introduced an MI regression: a failing MI sync execution
command misses printing the MI prompt, and then all subsequent command
miss it too:
$ gdb-7.11.1 -i=mi
[...]
p 1
&"p 1\n"
~"$1 = 1"
~"\n"
^done
(gdb) <<< prompted ok
-exec-continue
^error,msg="The program is not being run." <<< missing prompt after this
print 1
&"print 1\n"
~"$2 = 1"
~"\n"
^done <<< missing prompt after this
gdb 7.10.1 behaved correctly, even with "set mi-async on":
-exec-continue
^error,msg="The program is not being run."
(gdb) <<< prompted ok
etc.
Bisecting points at:
commit
|
||
---|---|---|
.. | ||
ChangeLog-1999-2003 | ||
mi-cmd-break.c | ||
mi-cmd-break.h | ||
mi-cmd-catch.c | ||
mi-cmd-disas.c | ||
mi-cmd-env.c | ||
mi-cmd-file.c | ||
mi-cmd-info.c | ||
mi-cmd-stack.c | ||
mi-cmd-target.c | ||
mi-cmd-var.c | ||
mi-cmds.c | ||
mi-cmds.h | ||
mi-common.c | ||
mi-common.h | ||
mi-console.c | ||
mi-console.h | ||
mi-getopt.c | ||
mi-getopt.h | ||
mi-interp.c | ||
mi-main.c | ||
mi-main.h | ||
mi-out.c | ||
mi-out.h | ||
mi-parse.c | ||
mi-parse.h | ||
mi-symbol-cmds.c |