[PATCH 19/28] Don't write to inferior_ptid in btrace_fetch

Pedro Alves
2020-04-14T17:54:53Z

AFAICT, this isn't required nowadays.

gdb/ChangeLog:
yyyy-mm-dd Pedro Alves <palves@redhat.com>

* btrace.c (btrace_fetch): Don't save/restore inferior_ptid.
---
gdb/btrace.c | 6 ------
1 file changed, 6 deletions(-)

diff --git a/gdb/btrace.c b/gdb/btrace.c
index bbf8749649..889507bfd2 100644
--- a/gdb/btrace.c
+++ b/gdb/btrace.c
@@ -1908,12 +1908,6 @@ btrace_fetch (struct thread_info *tp, const struct btrace_cpu *cpu)
if (btinfo->replay != NULL)
return;

- /* With CLI usage, TP->PTID always equals INFERIOR_PTID here. Now that we
- can store a gdb.Record object in Python referring to a different thread
- than the current one, temporarily set INFERIOR_PTID. */
- scoped_restore save_inferior_ptid = make_scoped_restore (&inferior_ptid);
- inferior_ptid = tp->ptid;
-
/* We should not be called on running or exited threads. */
gdb_assert (can_access_registers_thread (tp));

--
2.14.5