2005-05-29 03:13:19 +00:00
|
|
|
/* Interface for common GDB/MI data
|
2016-01-01 04:33:14 +00:00
|
|
|
Copyright (C) 2005-2016 Free Software Foundation, Inc.
|
2005-05-29 03:13:19 +00:00
|
|
|
|
|
|
|
This file is part of GDB.
|
|
|
|
|
|
|
|
This program is free software; you can redistribute it and/or modify
|
|
|
|
it under the terms of the GNU General Public License as published by
|
2007-08-23 18:08:50 +00:00
|
|
|
the Free Software Foundation; either version 3 of the License, or
|
2005-05-29 03:13:19 +00:00
|
|
|
(at your option) any later version.
|
|
|
|
|
|
|
|
This program is distributed in the hope that it will be useful,
|
|
|
|
but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
|
|
GNU General Public License for more details.
|
|
|
|
|
|
|
|
You should have received a copy of the GNU General Public License
|
2007-08-23 18:08:50 +00:00
|
|
|
along with this program. If not, see <http://www.gnu.org/licenses/>. */
|
2005-05-29 03:13:19 +00:00
|
|
|
|
|
|
|
#ifndef MI_COMMON_H
|
|
|
|
#define MI_COMMON_H
|
|
|
|
|
2011-01-06 00:57:05 +00:00
|
|
|
/* Represents the reason why GDB is sending an asynchronous command to
|
|
|
|
the front end. NOTE: When modifing this, don't forget to update
|
|
|
|
gdb.texinfo! */
|
2005-05-29 03:13:19 +00:00
|
|
|
enum async_reply_reason
|
|
|
|
{
|
|
|
|
EXEC_ASYNC_BREAKPOINT_HIT = 0,
|
|
|
|
EXEC_ASYNC_WATCHPOINT_TRIGGER,
|
|
|
|
EXEC_ASYNC_READ_WATCHPOINT_TRIGGER,
|
|
|
|
EXEC_ASYNC_ACCESS_WATCHPOINT_TRIGGER,
|
|
|
|
EXEC_ASYNC_FUNCTION_FINISHED,
|
|
|
|
EXEC_ASYNC_LOCATION_REACHED,
|
|
|
|
EXEC_ASYNC_WATCHPOINT_SCOPE,
|
|
|
|
EXEC_ASYNC_END_STEPPING_RANGE,
|
|
|
|
EXEC_ASYNC_EXITED_SIGNALLED,
|
|
|
|
EXEC_ASYNC_EXITED,
|
|
|
|
EXEC_ASYNC_EXITED_NORMALLY,
|
|
|
|
EXEC_ASYNC_SIGNAL_RECEIVED,
|
2011-11-22 21:25:19 +00:00
|
|
|
EXEC_ASYNC_SOLIB_EVENT,
|
|
|
|
EXEC_ASYNC_FORK,
|
|
|
|
EXEC_ASYNC_VFORK,
|
|
|
|
EXEC_ASYNC_SYSCALL_ENTRY,
|
|
|
|
EXEC_ASYNC_SYSCALL_RETURN,
|
|
|
|
EXEC_ASYNC_EXEC,
|
2005-05-29 03:13:19 +00:00
|
|
|
/* This is here only to represent the number of enums. */
|
|
|
|
EXEC_ASYNC_LAST
|
|
|
|
};
|
|
|
|
|
|
|
|
const char *async_reason_lookup (enum async_reply_reason reason);
|
|
|
|
|
2008-11-17 16:43:34 +00:00
|
|
|
struct mi_interp
|
|
|
|
{
|
|
|
|
/* MI's output channels */
|
|
|
|
struct ui_file *out;
|
|
|
|
struct ui_file *err;
|
|
|
|
struct ui_file *log;
|
|
|
|
struct ui_file *targ;
|
|
|
|
struct ui_file *event_channel;
|
|
|
|
|
2016-06-21 00:11:50 +00:00
|
|
|
/* Raw console output. */
|
|
|
|
struct ui_file *raw_stdout;
|
|
|
|
|
|
|
|
/* Save the original value of raw_stdout here when logging, so we
|
|
|
|
can restore correctly when done. */
|
|
|
|
struct ui_file *saved_raw_stdout;
|
|
|
|
|
2011-09-12 21:25:22 +00:00
|
|
|
/* MI's builder. */
|
PR gdb/13860 - Make MI sync vs async output (closer to) the same.
Ignoring expected and desired differences like whether the prompt is
output after *stoppped records, GDB MI output is still different in
sync and async modes.
In sync mode, when a CLI execution command is entered, the "reason"
field is missing in the *stopped async record. And in async mode, for
some events, like program exits, the corresponding CLI output is
missing in the CLI channel.
Vis, diff between sync vs async modes:
run
^running
*running,thread-id="1"
(gdb)
...
- ~"[Inferior 1 (process 15882) exited normally]\n"
=thread-exited,id="1",group-id="i1"
=thread-group-exited,id="i1",exit-code="0"
- *stopped
+ *stopped,reason="exited-normally"
si
...
(gdb)
~"0x000000000045e033\t29\t memset (&args, 0, sizeof args);\n"
- *stopped,frame=...,thread-id="1",stopped-threads="all",core="0"
+ *stopped,reason="end-stepping-range",frame=...,thread-id="1",stopped-threads="all",core="0"
(gdb)
In addition, in both cases, when a MI execution command is entered,
and a breakpoint triggers, the event is sent to the console too. But
some events like program exits have the CLI output missing in the CLI
channel:
-exec-run
^running
*running,thread-id="1"
(gdb)
...
=thread-exited,id="1",group-id="i1"
=thread-group-exited,id="i1",exit-code="0"
- *stopped
+ *stopped,reason="exited-normally"
We'll want to make background commands always possible by default.
IOW, make target-async be the default. But, in order to do that,
we'll need to emulate MI sync on top of an async target. That means
we'll have yet another combination to care for in the testsuite.
Rather than making the testsuite cope with all these differences, I
thought it better to just fix GDB to always have the complete output,
no matter whether it's in sync or async mode.
This is all related to interpreter-exec, and the corresponding uiout
switching. (Typing a CLI command directly in MI is shorthand for
running it through -interpreter-exec console.)
In sync mode, when a CLI command is active, normal_stop is called when
the current interpreter and uiout are CLI's. So print_XXX_reason
prints the stop reason to CLI uiout (only), and we don't show it in
MI.
In async mode the stop event is processed when we're back in the MI
interpreter, so the stop reason is printed directly to the MI uiout.
Fix this by making run control event printing roughly independent of
whatever is the current interpreter or uiout. That is, move these
prints to interpreter observers, that know whether to print or be
quiet, and if printing, which uiout to print to. In the case of the
console/tui interpreters, only print if the top interpreter. For MI,
always print.
Breakpoint hits / normal stops are already handled similarly -- MI has
a normal_stop observer that prints the event to both MI and the CLI,
though that could be cleaned up further in the direction of this
patch.
This also makes all of:
(gdb) foo
and
(gdb) interpreter-exec MI "-exec-foo"
and
(gdb)
-exec-foo
and
(gdb)
-interpreter-exec console "foo"
print as expected.
Tested on x86_64 Fedora 20, sync and async modes.
gdb/
2014-05-29 Pedro Alves <palves@redhat.com>
PR gdb/13860
* cli/cli-interp.c: Include infrun.h and observer.h.
(cli_uiout, cli_interp): New globals.
(cli_on_signal_received, cli_on_end_stepping_range)
(cli_on_signal_exited, cli_on_exited, cli_on_no_history): New
functions.
(cli_interpreter_init): Install them as 'end_stepping_range',
'signal_received' 'signal_exited', 'exited' and 'no_history'
observers.
(_initialize_cli_interp): Remove cli_interp local.
* infrun.c (handle_inferior_event): Call the several stop reason
observers instead of printing the stop reason directly.
(end_stepping_range): New function.
(print_end_stepping_range_reason, print_signal_exited_reason)
(print_exited_reason, print_signal_received_reason)
(print_no_history_reason): Make static, and add an uiout
parameter. Print to that instead of to CURRENT_UIOUT.
* infrun.h (print_end_stepping_range_reason)
(print_signal_exited_reason, print_exited_reason)
(print_signal_received_reason print_no_history_reason): New
declarations.
* mi/mi-common.h (struct mi_interp): Rename 'uiout' field to
'mi_uiout'.
<cli_uiout>: New field.
* mi/mi-interp.c (mi_interpreter_init): Adjust. Create the new
uiout for CLI output. Install 'signal_received',
'end_stepping_range', 'signal_exited', 'exited' and 'no_history'
observers.
(find_mi_interpreter, mi_interp_data, mi_on_signal_received)
(mi_on_end_stepping_range, mi_on_signal_exited, mi_on_exited)
(mi_on_no_history): New functions.
(ui_out_free_cleanup): Delete function.
(mi_on_normal_stop): Don't allocate a new uiout for CLI output,
instead use the one already stored in the MI interpreter data.
(mi_ui_out): Adjust.
* tui/tui-interp.c: Include infrun.h and observer.h.
(tui_interp): New global.
(tui_on_signal_received, tui_on_end_stepping_range)
(tui_on_signal_exited, tui_on_exited)
(tui_on_no_history): New functions.
(tui_init): Install them as 'end_stepping_range',
'signal_received' 'signal_exited', 'exited' and 'no_history'
observers.
(_initialize_tui_interp): Delete tui_interp local.
gdb/doc/
2014-05-29 Pedro Alves <palves@redhat.com>
PR gdb/13860
* observer.texi (signal_received, end_stepping_range)
(signal_exited, exited, no_history): New observer subjects.
gdb/testsuite/
2014-05-29 Pedro Alves <palves@redhat.com>
PR gdb/13860
* gdb.mi/mi-cli.exp: Always expect "end-stepping-range" stop
reason, even in sync mode.
2014-05-29 12:09:45 +00:00
|
|
|
struct ui_out *mi_uiout;
|
|
|
|
|
|
|
|
/* MI's CLI builder (wraps OUT). */
|
|
|
|
struct ui_out *cli_uiout;
|
2011-09-12 21:25:22 +00:00
|
|
|
|
2008-11-17 16:43:34 +00:00
|
|
|
/* This is the interpreter for the mi... */
|
|
|
|
struct interp *mi2_interp;
|
|
|
|
struct interp *mi1_interp;
|
|
|
|
struct interp *mi_interp;
|
|
|
|
};
|
|
|
|
|
2005-05-29 03:13:19 +00:00
|
|
|
#endif
|