mirror of
https://sourceware.org/git/binutils-gdb.git
synced 2024-11-30 21:44:19 +08:00
28addb40c7
When you use a run control command (-exec-run, -exec-continue,
-exec-next, ...) with mi-async on, an extra (gdb) prompt is displayed:
-exec-continue
^running
*running,thread-id="all"
(gdb)
(gdb)
It doesn't seem to be a big problem for front-ends, since this behavior
started in gdb 7.9 and we haven't heard anything about that. However,
it caused me some trouble while writing a test for PR 20039 [1].
The problem comes from an extra (gdb) prompt that we write when running
in mi-async off mode to emulate a past buggy behavior. When executing a
run control command synchronously, previous gdbs always printed a prompt
right away, even though they are not ready to accept new MI commands
until the target stops. Only at this time should they display a prompt.
But to keep backwards compatibility apparently, we print it anyway.
Since 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 |