[PATCH 0/2] Fix gdbserver/linux memory access regression

[Pedro Alves <pedro@palves.net>]

The recent change to make GDBserver always access memory via
/proc/pid/mem caused a regression in
gdb.threads/access-mem-running-thread-exit.exp that I somehow missed.
This is actually a pre-existing GDBserver issue being now exposed.

Patch #2 fixes the GDBserver bug.

Patch #1 fixes the gdb.threads/access-mem-running-thread-exit.exp
testcase itself -- it doesn't run properly against
--target_board=native-extended-gdbserver today.

Pedro Alves (2):
  Fix gdb.threads/access-mem-running-thread-exit.exp w/
    native-extended-gdbserver
  gdbserver: track current process as well as current thread

 .../access-mem-running-thread-exit.exp        | 30 ++++++++++++-
 gdbserver/gdbthread.h                         |  1 +
 gdbserver/inferiors.cc                        | 26 ++++++++---
 gdbserver/server.cc                           |  4 +-
 gdbserver/target.cc                           | 44 ++++++++++++++++++-
 gdbserver/target.h                            | 15 ++++++-
 6 files changed, 108 insertions(+), 12 deletions(-)


base-commit: 6ea673e2d643b7b2283aa73d35b02dfc9aa7115f
-- 
2.26.2