[PATCH 0/3] Stepping over clone syscall

Andrew Burgess andrew.burgess@embecosm.com
Wed Jun 30 19:55:01 GMT 2021


I ran into a situation where I needed to step over a clone syscall
with displaced stepping off.  I created bug PR gdb/27830 before I
really understood what the root cause of the problem was, but it is
all about stepping over a clone.

There is also bug gdb/19675 which is about stepping over a clone with
displaced stepping on, but that bug, though clearly related, is not
addressed by this series.

All feedback welcome.

Thanks,
Andrew

---

Andrew Burgess (3):
  gdb/testsuite: update test gdb.base/step-over-syscall.exp
  gdb: support stepping over a clone syscall with displaced stepping off
  gdb: non-displaced step over clone, remote target, no QThreadEvents

 gdb/ChangeLog                                 |  13 +
 gdb/infrun.c                                  |  31 ++
 gdb/testsuite/ChangeLog                       |  27 ++
 gdb/testsuite/gdb.base/step-over-clone.c      |  39 ++
 gdb/testsuite/gdb.base/step-over-syscall.exp  |  69 +++-
 gdb/testsuite/gdb.threads/stepi-over-clone.c  |  90 +++++
 .../gdb.threads/stepi-over-clone.exp          | 343 ++++++++++++++++++
 gdbserver/ChangeLog                           |   7 +
 gdbserver/linux-low.cc                        |  27 +-
 9 files changed, 628 insertions(+), 18 deletions(-)
 create mode 100644 gdb/testsuite/gdb.threads/stepi-over-clone.c
 create mode 100644 gdb/testsuite/gdb.threads/stepi-over-clone.exp

-- 
2.25.4



More information about the Gdb-patches mailing list