btrace: allow full memory and register access for non-replaying threads
authorMarkus Metzger <markus.t.metzger@intel.com>
Tue, 8 Sep 2015 07:05:38 +0000 (09:05 +0200)
committerMarkus Metzger <markus.t.metzger@intel.com>
Fri, 18 Sep 2015 12:29:22 +0000 (14:29 +0200)
commit4d10e986f499f330963c4641fd91046c57c94bd8
tree3c0e9fc1c87f7a33dc5c2957d1d76215cf4fe34e
parenta52eab48080f29feaa56421481cfea221ee6346e
btrace: allow full memory and register access for non-replaying threads

The record btrace target does not allow accessing memory and storing registers
while replaying.  For multi-threaded applications, this prevents those
accesses also for threads that are at the end of their execution history as
long as at least one thread is replaying.

Change this to only check if the selected thread is replaying.  This allows
threads that are at the end of their execution history to read and write
memory and to store registers.

Also change the error message to reflect this change.

gdb/
* record-btrace.c (record_btrace_xfer_partial)
(record_btrace_store_registers, record_btrace_prepare_to_store):
Call record_btrace_is_replaying with inferior_ptid instead of
minus_one_ptid.
(record_btrace_store_registers): Change error message.
gdb/ChangeLog
gdb/record-btrace.c
This page took 0.025047 seconds and 4 git commands to generate.