diff options
| author | Markus Metzger <markus.t.metzger@intel.com> | 2015-09-07 15:41:00 +0200 |
|---|---|---|
| committer | Markus Metzger <markus.t.metzger@intel.com> | 2015-09-18 14:32:00 +0200 |
| commit | f2665db5f2c20f3f47673ad5343738b10ce81dde (patch) | |
| tree | 4c92cf0fb7e8520751379a00d6b660f6b6420380 /gdb/NEWS | |
| parent | 7ff27e9babb1564a9c0e213c4a42396aa420f8cc (diff) | |
| download | gdb-f2665db5f2c20f3f47673ad5343738b10ce81dde.zip gdb-f2665db5f2c20f3f47673ad5343738b10ce81dde.tar.gz gdb-f2665db5f2c20f3f47673ad5343738b10ce81dde.tar.bz2 | |
infrun: scheduler-locking replay
Record targets behave as if scheduler-locking were on in replay mode. Add a
new scheduler-locking option "replay" to make this implicit behaviour explicit.
It behaves like "on" in replay mode and like "off" in record mode.
By making the current behaviour a scheduler-locking option, we allow the user
to change it. Since it is the current behaviour, this new option is also
the new default.
One caveat is that when resuming a thread that is at the end of its execution
history, record btrace implicitly stops replaying other threads and resumes
the entire process. This is a convenience feature to not require the user
to explicitly move all other threads to the end of their execution histories
before being able to resume the process.
We mimick this behaviour with scheduler-locking replay and move it from
record-btrace into infrun. With all-stop on top of non-stop, we can't do
this in record-btrace anymore.
Record full does not really support multi-threading and is therefore not
impacted. If it were extended to support multi-threading, it would 'benefit'
from this change. The good thing is that all record targets will behave the
same with respect to scheduler-locking.
I put the code for this into clear_proceed_status. It also sends the
about_to_proceed notification.
gdb/
* NEWS: Announce new scheduler-locking mode.
* infrun.c (schedlock_replay): New.
(scheduler_enums): Add schedlock_replay.
(scheduler_mode): Change default to schedlock_replay.
(user_visible_resume_ptid): Handle schedlock_replay.
(clear_proceed_status_thread): Stop replaying if resumed thread is
not replaying.
(schedlock_applies): Handle schedlock_replay.
(_initialize_infrun): Document new scheduler-locking mode.
* record-btrace.c (record_btrace_resume): Remove code to stop other
threads when not replaying the resumed thread.
doc/
* gdb.texinfo (All-Stop Mode): Describe new scheduler-locking mode.
Diffstat (limited to 'gdb/NEWS')
| -rw-r--r-- | gdb/NEWS | 3 |
1 files changed, 3 insertions, 0 deletions
@@ -45,6 +45,9 @@ show remote multiprocess-extensions-packet The "/m" option is now considered deprecated: its "source-centric" output hasn't proved useful in practice. +* The "set scheduler-locking" command supports a new mode "replay". + It behaves like "off" in record mode and like "on" in replay mode. + * Support for various ROM monitors has been removed: target dbug dBUG ROM monitor for Motorola ColdFire |