gdb: add target_ops::supports_displaced_step concurrent-displaced-stepping-2020-04-01
authorSimon Marchi <simon.marchi@efficios.com>
Tue, 7 Apr 2020 15:30:46 +0000 (11:30 -0400)
committerSimon Marchi <simon.marchi@efficios.com>
Thu, 4 Jun 2020 19:04:21 +0000 (15:04 -0400)
commit65a7e4d60ff61d720e7b1755937fa7e871ef8e4b
tree199ded44b017d1810a144f66402b1fa8e1a1ae6f
parent5514706f739978e0897d01ec9fa25fa61861c263
gdb: add target_ops::supports_displaced_step

A previous patch added some `displaced_step_prepare` and
`displaced_step_finish` methods to allow a target_ops to implement
displaced stepping.  The default implementation is to defer to the
gdbarch.

However, there is still a `gdbarch_supports_displaced_stepping` check in
infrun.c, that decides if we should use displaced stepping or not.  So
if a target_ops implemented displaced stepping, independently of the
gdbarch, displaced stepping wouldn't be used.

Add the target_ops::supports_displaced_step method, with a default
behavior of checking if the gdbarch supports it (which is in sync with
the default implementations of displaced_step_prepare and
displaced_step_finish).
gdb/displaced-stepping.c
gdb/displaced-stepping.h
gdb/infrun.c
gdb/target-delegates.c
gdb/target.h
This page took 0.024099 seconds and 4 git commands to generate.