This is the mail archive of the
gdb-cvs@sourceware.org
mailing list for the GDB project.
gdb and binutils branch master updated. e59fa00fa07f37aa04d38aecaf8098e01aaf253d
- From: mmetzger at sourceware dot org
- To: gdb-cvs at sourceware dot org
- Date: 20 May 2014 12:20:33 -0000
- Subject: gdb and binutils branch master updated. e59fa00fa07f37aa04d38aecaf8098e01aaf253d
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 e59fa00fa07f37aa04d38aecaf8098e01aaf253d (commit)
from 00b32ff21f710a5eed92c9fdf51c32103bcc4176 (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=e59fa00fa07f37aa04d38aecaf8098e01aaf253d
commit e59fa00fa07f37aa04d38aecaf8098e01aaf253d
Author: Markus Metzger <markus.t.metzger@intel.com>
Date: Thu May 15 10:57:36 2014 +0200
btrace: no replay without history
When using a reverse execution command without execution history, GDB
might end up in a state where replaying has been started but remains
at the current instruction. This state is illegal.
Do not step if there is no execution history to avoid this.
2014-05-20 Markus Metzger <markus.t.metzger@intel.com>
* record-btrace.c (record_btrace_step_thread): Check for empty history.
testsuite/
* gdb.btrace/nohist.exp: New.
-----------------------------------------------------------------------
Summary of changes:
gdb/ChangeLog | 4 +++
gdb/record-btrace.c | 4 +++
gdb/testsuite/ChangeLog | 4 +++
gdb/testsuite/gdb.btrace/{data.exp => nohist.exp} | 27 +++++++++++----------
4 files changed, 26 insertions(+), 13 deletions(-)
copy gdb/testsuite/gdb.btrace/{data.exp => nohist.exp} (66%)
hooks/post-receive
--
gdb and binutils