This is the mail archive of the
gdb-cvs@sourceware.org
mailing list for the GDB project.
gdb and binutils branch master updated. 589fdceb99db9868e34bc976b7e234dbfaf327e2
- From: mmetzger at sourceware dot org
- To: gdb-cvs at sourceware dot org
- Date: 23 May 2014 07:13:36 -0000
- Subject: gdb and binutils branch master updated. 589fdceb99db9868e34bc976b7e234dbfaf327e2
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gdb and binutils".
The branch, master has been updated
via 589fdceb99db9868e34bc976b7e234dbfaf327e2 (commit)
via e9089e05b6a1a89ba6b8f3123f9d76bf066e3db7 (commit)
via 67b5c0c1a4336318f23f65b8fa98a08b569c5c39 (commit)
from 4c6bdb4026d3c7050aacade3fa5340dfaa491bc1 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=589fdceb99db9868e34bc976b7e234dbfaf327e2
commit 589fdceb99db9868e34bc976b7e234dbfaf327e2
Author: Markus Metzger <markus.t.metzger@intel.com>
Date: Wed Apr 2 09:54:11 2014 +0200
btrace, vdso: add vdso target sections
When loading symbols for the vdso, also add its sections to target_sections.
This fixes an issue with record btrace where vdso instructions could not be
disassembled during replay.
* symfile-mem.c (symbol_file_add_from_memory): Add BFD sections.
testsuite/
* gdb.btrace/vdso.c: New.
* gdb.btrace/vdso.exp: New.
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=e9089e05b6a1a89ba6b8f3123f9d76bf066e3db7
commit e9089e05b6a1a89ba6b8f3123f9d76bf066e3db7
Author: Markus Metzger <markus.t.metzger@intel.com>
Date: Tue May 20 09:48:43 2014 +0200
test, gcore: move capture_command_output into lib/gdb.exp
Allow gcore's capture_command_output function to be used by other tests.
testsuite/
* gdb.base/gcore.exp (capture_command_output): Move ...
* lib/gdb.exp (capture_command_output): ... here.
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=67b5c0c1a4336318f23f65b8fa98a08b569c5c39
commit 67b5c0c1a4336318f23f65b8fa98a08b569c5c39
Author: Markus Metzger <markus.t.metzger@intel.com>
Date: Wed Mar 5 15:38:11 2014 +0100
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.
-----------------------------------------------------------------------
Summary of changes:
gdb/ChangeLog | 18 ++++++++
gdb/NEWS | 4 ++
gdb/doc/ChangeLog | 5 ++
gdb/doc/gdb.texinfo | 22 +++++++++
gdb/record-btrace.c | 88 ++++++++++++++++++++++++++++++++-----
gdb/symfile-mem.c | 18 ++++++++
gdb/testsuite/ChangeLog | 14 ++++++
gdb/testsuite/gdb.base/gcore.exp | 13 -----
gdb/testsuite/gdb.btrace/data.exp | 10 ++++-
gdb/testsuite/gdb.btrace/vdso.c | 30 +++++++++++++
gdb/testsuite/gdb.btrace/vdso.exp | 53 ++++++++++++++++++++++
gdb/testsuite/lib/gdb.exp | 14 ++++++
12 files changed, 264 insertions(+), 25 deletions(-)
create mode 100644 gdb/testsuite/gdb.btrace/vdso.c
create mode 100644 gdb/testsuite/gdb.btrace/vdso.exp
hooks/post-receive
--
gdb and binutils