public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sourceware.org
Cc: zhiyong.yan@windriver.com, simon.marchi@polymtl.ca,
	Kevin Buettner <kevinb@redhat.com>
Subject: [PATCH 0/1] gdbserver: Reinstall software single-step breakpoints in resume_stopped_resumed_lwps
Date: Wed,  2 Aug 2023 17:56:00 -0700	[thread overview]
Message-ID: <20230803011146.2093194-1-kevinb@redhat.com> (raw)

This patch fixes a problem with software single-stepping in gdbserver.
See the 1/1 patch for the details.

The fix proper is based on the work of Zhiyong Yan, who I've credited
with a Co-Authored-By tag in the 1/1 patch.  The test case was also
partly Zhiyong's work since I adapted the C file from the reproducer
in the bug that was filed for this problem.

Zhiyong, please check to make sure that this revised change to
gdbserver/linux-low.c still fixes the bug on your board.

I've added Simon as a CC since the .exp file for the new test is based
on gdb.threads/next-fork-other-thread.exp, which he authored.  Also,
from my reading of the commit log for that test, I gather that Simon
has looked at a related problem in the past.

Kevin Buettner (1):
  gdbserver: Reinstall software single-step breakpoints in
    resume_stopped_resumed_lwps

 .../gdb.threads/next-fork-exec-other-thread.c |  82 +++++++++++
 .../next-fork-exec-other-thread.exp           | 131 ++++++++++++++++++
 gdbserver/linux-low.cc                        |   7 +-
 3 files changed, 219 insertions(+), 1 deletion(-)
 create mode 100644 gdb/testsuite/gdb.threads/next-fork-exec-other-thread.c
 create mode 100644 gdb/testsuite/gdb.threads/next-fork-exec-other-thread.exp

-- 
2.41.0


             reply	other threads:[~2023-08-03  1:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-03  0:56 Kevin Buettner [this message]
2023-08-03  0:56 ` [PATCH 1/1] " Kevin Buettner
2023-08-07 10:54   ` Yan, Zhiyong
2023-08-08  2:31     ` Kevin Buettner
2023-08-08  2:39       ` Yan, Zhiyong
2023-08-08  2:52         ` Kevin Buettner
2023-08-12  4:00   ` Kevin Buettner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230803011146.2093194-1-kevinb@redhat.com \
    --to=kevinb@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@polymtl.ca \
    --cc=zhiyong.yan@windriver.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).