public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Cc: Andrew Burgess <aburgess@redhat.com>
Subject: [PATCH 0/2] Missing thread events for remote targets
Date: Wed, 11 Oct 2023 13:53:11 +0100	[thread overview]
Message-ID: <cover.1697028568.git.aburgess@redhat.com> (raw)

I noticed that in some situations we are missing thread events ('new
thead' and 'thread exited') when using a remote target.  The second
patch in this series addresses this issue.

While writing the test for this case I discovered that
$_inferior_thread_count doesn't always give the correct value when
using remote targets, so the first patch addresses this issue.

---

Andrew Burgess (2):
  gdb: call update_thread_list for $_inferior_thread_count function
  gdb: call update_thread_list after completing an inferior call

 gdb/infcall.c                                 |   7 +
 gdb/testsuite/gdb.threads/inf-thr-count.c     |  80 ++++++++
 gdb/testsuite/gdb.threads/inf-thr-count.exp   | 175 ++++++++++++++++
 .../gdb.threads/infcall-thread-announce.c     | 192 ++++++++++++++++++
 .../gdb.threads/infcall-thread-announce.exp   |  71 +++++++
 gdb/thread.c                                  |   2 +
 6 files changed, 527 insertions(+)
 create mode 100644 gdb/testsuite/gdb.threads/inf-thr-count.c
 create mode 100644 gdb/testsuite/gdb.threads/inf-thr-count.exp
 create mode 100644 gdb/testsuite/gdb.threads/infcall-thread-announce.c
 create mode 100644 gdb/testsuite/gdb.threads/infcall-thread-announce.exp


base-commit: f6ca448ab70c52e923b7010aecdf7be9c0d4d4fc
-- 
2.25.4


             reply	other threads:[~2023-10-11 12:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-11 12:53 Andrew Burgess [this message]
2023-10-11 12:53 ` [PATCH 1/2] gdb: call update_thread_list for $_inferior_thread_count function Andrew Burgess
2023-10-11 12:53 ` [PATCH 2/2] gdb: call update_thread_list after completing an inferior call Andrew Burgess
2023-11-08 13:30 ` [PATCH 0/2] Missing thread events for remote targets Andrew Burgess

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=cover.1697028568.git.aburgess@redhat.com \
    --to=aburgess@redhat.com \
    --cc=gdb-patches@sourceware.org \
    /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).