fix record "run" regression
authorTom Tromey <tromey@redhat.com>
Tue, 1 Jul 2014 17:43:00 +0000 (11:43 -0600)
committerTom Tromey <tromey@redhat.com>
Mon, 14 Jul 2014 14:33:05 +0000 (08:33 -0600)
commit548740d6bdd115da2c9c17b194016c2c4c0a4c69
treec6d07c4fc8f734c515bdd150d9b6e68d95c6c218
parent0ed82684efcb5243b66f918552403ff4ec1d7ee1
fix record "run" regression

This fixes the record "run" regression pointed out by Marc Khouzam:

    https://sourceware.org/ml/gdb/2014-06/msg00096.html

The bug is that target_require_runnable must agree with the handling
of the "run" target, but currently it is out of sync.  This patch
fixes the problem by changing target_require_runnable to also ignore
the record_stratum.

Built and regtested on x86-64 Fedora 20.
New test case included.

2014-07-14  Tom Tromey  <tromey@redhat.com>

* target.c (target_require_runnable): Also check record_stratum.
Update comment.

2014-07-14  Tom Tromey  <tromey@redhat.com>

* gdb.reverse/rerun-prec.c: New file.
* gdb.reverse/rerun-prec.exp: New file.
gdb/ChangeLog
gdb/target.c
gdb/testsuite/ChangeLog
gdb/testsuite/gdb.reverse/rerun-prec.c [new file with mode: 0644]
gdb/testsuite/gdb.reverse/rerun-prec.exp [new file with mode: 0644]