This is the mail archive of the
gdb-testers@sourceware.org
mailing list for the GDB project.
[binutils-gdb] New function should_print_stop_to_console
- From: sergiodj+buildbot at sergiodj dot net
- To: gdb-testers at sourceware dot org
- Date: Fri, 15 Jul 2016 02:24:55 -0400
- Subject: [binutils-gdb] New function should_print_stop_to_console
- Authentication-results: sourceware.org; auth=none
*** TEST RESULTS FOR COMMIT 26cde2cc30c25ba4d5666ea502db51ee6cb5b069 ***
Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 26cde2cc30c25ba4d5666ea502db51ee6cb5b069
New function should_print_stop_to_console
There's code in the MI interpreter that decides whether a stop should
be sent to MI's console stream. Move this check to the CLI
interpreter code, so that we can reuse it in both the CLI and TUI
interpreters.
gdb/ChangeLog:
2016-06-21 Pedro Alves <palves@redhat.com>
* cli/cli-interp.c: Include gdbthread.h and thread-fsm.h.
(should_print_stop_to_console): New function, factored out from
mi_on_normal_stop_1.
* cli/cli-interp.h (should_print_stop_to_console): Declare.
* mi/mi-interp.c (mi_on_normal_stop_1): Use
should_print_stop_to_console. Pass it the current UI's console
interpreter.
* mi/mi-main.c (captured_mi_execute_command): Use the
INTERP_CONSOLE symbol rather than explicit "console".