summaryrefslogtreecommitdiff
path: root/gdbserver/target.h
diff options
context:
space:
mode:
authorPedro Alves <pedro@palves.net>2022-04-05 13:57:11 +0100
committerPedro Alves <pedro@palves.net>2022-05-03 15:10:22 +0100
commit7f8acedeebe295fc8cc1d11ed971cbfc1942618c (patch)
treeb07af08ce2cf645c90836a4bcf77c3a68c475780 /gdbserver/target.h
parentf4138e8f48948314d1049e713f4b793eec9757ca (diff)
gdbserver: track current process as well as current thread
The recent commit 421490af33bf ("gdbserver/linux: Access memory even if threads are running") caused a regression in gdb.threads/access-mem-running-thread-exit.exp with gdbserver, which I somehow missed. Like so: (gdb) print global_var Cannot access memory at address 0x555555558010 (gdb) FAIL: gdb.threads/access-mem-running-thread-exit.exp: non-stop: access mem (print global_var after writing, inf=2, iter=1) The problem starts with GDB telling GDBserver to select a thread, via the Hg packet, which GDBserver complies with, then that thread exits, and GDB, without knowing the thread is gone, tries to write to memory, through the context of the previously selected Hg thread. GDBserver's GDB-facing memory access routines, gdb_read_memory and gdb_write_memory, call set_desired_thread to make GDBserver re-select the thread that GDB has selected with the Hg packet. Since the thread is gone, set_desired_thread returns false, and the memory access fails. Now, to access memory, it doesn't really matter which thread is selected. All we should need is the target process. Even if the thread that GDB previously selected is gone, and GDB does not yet know about that exit, it shouldn't matter, GDBserver should still know which process that thread belonged to. Fix this by making GDBserver track the current process separately, like GDB also does. Add a new set_desired_process routine that is similar to set_desired_thread, but just sets the current process, leaving the current thread as NULL. Use it in the GDB-facing memory read and write routines, to avoid failing if the selected thread is gone, but the process is still around. Change-Id: I4ff97cb6f42558efbed224b30d5c71f6112d44cd
Diffstat (limited to 'gdbserver/target.h')
-rw-r--r--gdbserver/target.h15
1 files changed, 14 insertions, 1 deletions
diff --git a/gdbserver/target.h b/gdbserver/target.h
index f3172e2ed7..6c536a3077 100644
--- a/gdbserver/target.h
+++ b/gdbserver/target.h
@@ -699,7 +699,20 @@ target_thread_pending_child (thread_info *thread)
int read_inferior_memory (CORE_ADDR memaddr, unsigned char *myaddr, int len);
-int set_desired_thread ();
+/* Set GDBserver's current thread to the thread the client requested
+ via Hg. Also switches the current process to the requested
+ process. If the requested thread is not found in the thread list,
+ then the current thread is set to NULL. Likewise, if the requested
+ process is not found in the process list, then the current process
+ is set to NULL. Returns true if the requested thread was found,
+ false otherwise. */
+
+bool set_desired_thread ();
+
+/* Set GDBserver's current process to the process the client requested
+ via Hg. The current thread is set to NULL. */
+
+bool set_desired_process ();
std::string target_pid_to_str (ptid_t);