btrace: honour scheduler-locking for all-stop targets
authorMarkus Metzger <markus.t.metzger@intel.com>
Wed, 16 Sep 2015 07:05:22 +0000 (09:05 +0200)
committerMarkus Metzger <markus.t.metzger@intel.com>
Fri, 18 Sep 2015 12:33:16 +0000 (14:33 +0200)
commitd2939ba2b40daa89b501d4b81484ea888ef17139
tree12f688476388b1eaf825613f434067b19212dcbc
parentf2665db5f2c20f3f47673ad5343738b10ce81dde
btrace: honour scheduler-locking for all-stop targets

In all-stop mode, record btrace maintains the old behaviour of an implicit
scheduler-locking on.

Now that we added a scheduler-locking mode to model this old behaviour, we
don't need the respective code in record btrace anymore.  Remove it.

For all-stop targets, step inferior_ptid and continue other threads matching
the argument ptid.  Assert that inferior_ptid matches the argument ptid.

This should make record btrace honour scheduler-locking.

gdb/
* record-btrace.c (record_btrace_resume): Honour scheduler-locking.

testsuite/
* gdb.btrace/multi-thread-step.exp: Test scheduler-locking on, step,
and replay.
gdb/ChangeLog
gdb/record-btrace.c
gdb/testsuite/ChangeLog
gdb/testsuite/gdb.btrace/multi-thread-step.exp
This page took 0.035313 seconds and 4 git commands to generate.