diff options
| author | Markus Metzger <markus.t.metzger@intel.com> | 2014-03-05 15:38:11 +0100 |
|---|---|---|
| committer | Markus Metzger <markus.t.metzger@intel.com> | 2014-05-23 09:07:53 +0200 |
| commit | 67b5c0c1a4336318f23f65b8fa98a08b569c5c39 (patch) | |
| tree | 476287feb650f7f662c4afae6e22cc5677ef7bc3 /gdb/doc | |
| parent | 4c6bdb4026d3c7050aacade3fa5340dfaa491bc1 (diff) | |
| download | gdb-67b5c0c1a4336318f23f65b8fa98a08b569c5c39.zip gdb-67b5c0c1a4336318f23f65b8fa98a08b569c5c39.tar.gz gdb-67b5c0c1a4336318f23f65b8fa98a08b569c5c39.tar.bz2 | |
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.
Diffstat (limited to 'gdb/doc')
| -rw-r--r-- | gdb/doc/ChangeLog | 5 | ||||
| -rw-r--r-- | gdb/doc/gdb.texinfo | 22 |
2 files changed, 27 insertions, 0 deletions
diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog index 18588f6..25bdc32 100644 --- a/gdb/doc/ChangeLog +++ b/gdb/doc/ChangeLog @@ -1,3 +1,8 @@ +2014-05-23 Markus Metzger <markus.t.metzger@intel.com> + + * gdb.texinfo (Process Record and Replay): Document "set/show btrace + replay-memory-access". + 2014-05-21 Pedro Alves <palves@redhat.com> * gdb.texinfo (Starting): Document "set/show diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index 47d4bb7..cc188ae 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -6451,6 +6451,28 @@ results. @item show record full memory-query Show the current setting of @code{memory-query}. +@kindex set record btrace +The @code{btrace} record target does not trace data. As a +convenience, when replaying, @value{GDBN} reads read-only memory off +the live program directly, assuming that the addresses of the +read-only areas don't change. This for example makes it possible to +disassemble code while replaying, but not to print variables. +In some cases, being able to inspect variables might be useful. +You can use the following command for that: + +@item set record btrace replay-memory-access +Control the behavior of the @code{btrace} recording method when +accessing memory during replay. If @code{read-only} (the default), +@value{GDBN} will only allow accesses to read-only memory. +If @code{read-write}, @value{GDBN} will allow accesses to read-only +and to read-write memory. Beware that the accessed memory corresponds +to the live target and not necessarily to the current replay +position. + +@kindex show record btrace +@item show record btrace replay-memory-access +Show the current setting of @code{replay-memory-access}. + @kindex info record @item info record Show various statistics about the recording depending on the recording |