diff options
author | Simon Marchi <simon.marchi@ericsson.com> | 2016-12-08 13:06:14 -0500 |
---|---|---|
committer | Simon Marchi <simon.marchi@ericsson.com> | 2017-02-23 17:25:30 -0500 |
commit | 44c04ee9bf959b40819de6327500557fbb5d8c4a (patch) | |
tree | f2fae0b73585f6b67cfbb0f7c29d65f9d70ebc77 /gdb/inferior.c | |
parent | a567769b813b2538bebc97d689fc0739f172028e (diff) | |
download | binutils-users/simark/user-selection-rfc.zip binutils-users/simark/user-selection-rfc.tar.gz binutils-users/simark/user-selection-rfc.tar.bz2 |
Decouple user selection from internal selectionusers/simark/user-selection-rfc
I am sending this as an RFC because it's far from complete and
definitive, but I'd like to gather some comments and opinions before
going further in this direction.
The goal of this patch is to decouple the notion of the user-selected
inferior/thread/frame from GDB's internally selected
inferior/thread/frame.
Currently, for example, the inferior_ptid variable has two jobs:
- it's the user-selected thread: it's changed by the "thread" command.
Other commands (continue, backtrace, etc) apply to this thread.
- it's the internally-selected thread: it defines the thread GDB is
currently "working" on. For example, implementations of
to_xfer_partial will refer to it to know from which thread to
read/write memory.
Because of this dual usage, if we want to do some operations on a thread
other than the currently selected one, we have to save the current
inferior/thread/frame and restore them when we're done. Failing to do
so would result in an unexpected selection switch for the user.
To improve this, Pedro suggested in [1] to decouple the two concepts. This
is essentially what this patch is trying to do.
A new "user_selection" object is introduced, which contains the selected
inferior/thread/frame from the point of view of the user. Before every
command, we "apply" this selection to the core of GDB to make sure the
internal selection matches the user selection.
There is a single user selection for the whole GDB (named "global
user-selection"), but as was mentioned in the linked thread, it opens
the door to having different selections for different UIs. This means
that each UI would have its own user-selection object, which would be
applied to the core prior to executing commands from this UI.
The global user-selection object only gets modified when we really
intend to change it. It can be because of the thread / -thread-select /
up / down / frame / inferior commands, a breakpoint hit in all-stop, an
inferior exit, etc.
The problem that initially prompted this effort is that the "--thread"
flag of MI commands changes the user-selected thread under the user's
feet. My initial attempt to fix it was to restore the selection after
the MI command execution. However, some cases are hard to get right.
For example:
(thread 1 is currently selected)
-interpreter-exec --thread 2 console "thread 3"
Restoring the selected thread to thread 1 after the MI command execution
wrongfully cancels the switch to thread 3. So it's hard to determine
when we should or shouldn't restore. With the current patch, it works
naturally: the --thread flag doesn't touch the user-selected thread,
only the internal one. The "thread 3" command updates the user
selection.
Another difficulty is to send the right notifications to MI when the
user selection changes. That means to not miss any, but not send too
many either. Getting it somewhat right lead to ugly hacks (see the
command_notifies_uscc_observer function) and even then it's not perfect
(see the kfails in user-selected-context-sync.exp test). With the
proposed method, it's easy to know when the user-selection changes and
send notifications.
With this patch, there are probably a few usage of
make_cleanup_restore_current_thread that are not needed anymore, if they
are only used to restore the user selection. I kept removing them for a
later time though.
In the current state, there are a few minor regressions in the testsuite
(especially some follow-fork stuff I'm not sure how to handle), but the
vast majority of the previously passing tests still pass.
Comments are welcome!
Thanks,
Simon
[1] https://sourceware.org/ml/gdb-patches/2016-08/msg00031.html
Diffstat (limited to 'gdb/inferior.c')
-rw-r--r-- | gdb/inferior.c | 44 |
1 files changed, 14 insertions, 30 deletions
diff --git a/gdb/inferior.c b/gdb/inferior.c index c4ab6d7..d9d026a 100644 --- a/gdb/inferior.c +++ b/gdb/inferior.c @@ -35,6 +35,7 @@ #include "arch-utils.h" #include "target-descriptions.h" #include "readline/tilde.h" +#include "user-selection.h" void _initialize_inferiors (void); @@ -554,9 +555,8 @@ inferior_pid_to_str (int pid) /* See inferior.h. */ void -print_selected_inferior (struct ui_out *uiout) +print_selected_inferior (struct ui_out *uiout, struct inferior *inf) { - struct inferior *inf = current_inferior (); const char *filename = inf->pspace->pspace_exec_filename; if (filename == NULL) @@ -566,8 +566,7 @@ print_selected_inferior (struct ui_out *uiout) inf->num, inferior_pid_to_str (inf->pid), filename); } -/* Prints the list of inferiors and their details on UIOUT. This is a - version of 'info_inferior_command' suitable for use from MI. +/* Prints the list of inferiors and their details on UIOUT. If REQUESTED_INFERIORS is not NULL, it's a list of GDB ids of the inferiors that should be printed. Otherwise, all inferiors are @@ -579,6 +578,7 @@ print_inferior (struct ui_out *uiout, char *requested_inferiors) struct inferior *inf; struct cleanup *old_chain; int inf_count = 0; + struct inferior *selected_inferior = global_user_selection ()->inferior (); /* Compute number of inferiors we will print. */ for (inf = inferior_list; inf; inf = inf->next) @@ -612,7 +612,7 @@ print_inferior (struct ui_out *uiout, char *requested_inferiors) chain2 = make_cleanup_ui_out_tuple_begin_end (uiout, NULL); - if (inf == current_inferior ()) + if (inf == selected_inferior) uiout->field_string ("current", "*"); else uiout->field_skip ("current"); @@ -732,6 +732,7 @@ inferior_command (char *args, int from_tty) { struct inferior *inf; int num; + user_selection *us = global_user_selection (); num = parse_and_eval_long (args); @@ -739,31 +740,12 @@ inferior_command (char *args, int from_tty) if (inf == NULL) error (_("Inferior ID %d not known."), num); - if (inf->pid != 0) + /* Keep the old behavior of printing "Switching to inferior X" even if it was + already the selected inferior. */ + if (!us->select_inferior (inf, true)) { - if (inf->pid != ptid_get_pid (inferior_ptid)) - { - struct thread_info *tp; - - tp = any_thread_of_process (inf->pid); - if (!tp) - error (_("Inferior has no threads.")); - - switch_to_thread (tp->ptid); - } - - observer_notify_user_selected_context_changed - (USER_SELECTED_INFERIOR - | USER_SELECTED_THREAD - | USER_SELECTED_FRAME); - } - else - { - set_current_inferior (inf); - switch_to_thread (null_ptid); - set_current_program_space (inf->pspace); - - observer_notify_user_selected_context_changed (USER_SELECTED_INFERIOR); + print_selected_inferior (current_uiout, us->inferior ()); + print_selected_thread_frame (current_uiout, us, USER_SELECTED_THREAD | USER_SELECTED_FRAME); } } @@ -783,6 +765,8 @@ remove_inferior_command (char *args, int from_tty) if (args == NULL || *args == '\0') error (_("Requires an argument (inferior id(s) to remove)")); + struct inferior *selected_inferior = global_user_selection ()->inferior (); + number_or_range_parser parser (args); while (!parser.finished ()) { @@ -795,7 +779,7 @@ remove_inferior_command (char *args, int from_tty) continue; } - if (inf == current_inferior ()) + if (inf == selected_inferior) { warning (_("Can not remove current inferior %d."), num); continue; |