btrace: control memory access during replay
authorMarkus Metzger <markus.t.metzger@intel.com>
Wed, 5 Mar 2014 14:38:11 +0000 (15:38 +0100)
committerMarkus Metzger <markus.t.metzger@intel.com>
Fri, 23 May 2014 07:07:53 +0000 (09:07 +0200)
commit67b5c0c1a4336318f23f65b8fa98a08b569c5c39
tree476287feb650f7f662c4afae6e22cc5677ef7bc3
parent4c6bdb4026d3c7050aacade3fa5340dfaa491bc1
btrace: control memory access during replay

The btrace record target does not trace data.  We therefore do not allow
accessing read-write memory during replay.

In some cases, this might be useful to advanced users, though, who we assume
to know what they are doing.

Add a set|show command pair to turn this memory access restriction off.

* record-btrace.c (record_btrace_allow_memory_access): Remove.
(replay_memory_access_read_only, replay_memory_access_read_write)
(replay_memory_access_types, replay_memory_access)
(set_record_btrace_cmdlist, show_record_btrace_cmdlist)
(cmd_set_record_btrace, cmd_show_record_btrace)
(cmd_show_replay_memory_access): New.
(record_btrace_xfer_partial, record_btrace_insert_breakpoint)
(record_btrace_remove_breakpoint): Replace
record_btrace_allow_memory_access with replay_memory_access.
(_initialize_record_btrace): Add commands.
* NEWS: Announce it.

testsuite/
* gdb.btrace/data.exp: Test it.

doc/
* gdb.texinfo (Process Record and Replay): Document it.
gdb/ChangeLog
gdb/NEWS
gdb/doc/ChangeLog
gdb/doc/gdb.texinfo
gdb/record-btrace.c
gdb/testsuite/ChangeLog
gdb/testsuite/gdb.btrace/data.exp
This page took 0.027023 seconds and 4 git commands to generate.