displaced step: pass down target_waitstatus instead of gdb_signal
authorPedro Alves <pedro@palves.net>
Tue, 22 Jun 2021 14:42:51 +0000 (15:42 +0100)
committerPedro Alves <pedro@palves.net>
Mon, 27 Mar 2023 16:17:20 +0000 (17:17 +0100)
commit58c010877e77ad9dd4e14272f9500d40b75e7429
tree14d9819aa812ac37a985946f408ad4bfe0de8f10
parent1e77fa23a02f54be87a79a4931c8ee1d696b3981
displaced step: pass down target_waitstatus instead of gdb_signal

This commit tweaks displaced_step_finish & friends to pass down a
target_waitstatus instead of a gdb_signal.  This is needed because a
patch later in the step-over-{thread-exit,clone] series will want to
make displaced_step_buffers::finish handle
TARGET_WAITKIND_THREAD_EXITED.  It also helps with the
TARGET_WAITKIND_THREAD_CLONED patch later in that same series.

It's also a bit more logical this way, as we don't have to pass down
signals when the thread didn't actually stop for a signal.  So we can
also think of it as a clean up.

Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=27338
Change-Id: I4c5d338647b028071bc498c4e47063795a2db4c0
Approved-By: Andrew Burgess <aburgess@redhat.com>
gdb/displaced-stepping.c
gdb/displaced-stepping.h
gdb/gdbarch-gen.h
gdb/gdbarch.c
gdb/gdbarch_components.py
gdb/infrun.c
gdb/linux-tdep.c
gdb/linux-tdep.h
gdb/rs6000-tdep.c