Mirror of the gdb-patches mailing list
 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/3] Better error handling when creating threads with clone()
Date: Tue,  7 Apr 2026 11:22:26 +0100	[thread overview]
Message-ID: <cover.1775557188.git.aburgess@redhat.com> (raw)

A Fedora GDB bug got me looking at error handling relating to GDB's
clone handling, and thread-db thread adoption.

The first two patches are some refactoring in this area, and the third
patch changes and improves error handling so that GDB is better able
to track threads even if thread-db thread adoption fails.

Thanks,
Andrew

---

Andrew Burgess (3):
  gdb: int to bool conversion in linux-thread-db.c
  gdb: add some asserts to thread_db_notice_clone
  gdb: improve error handling for thread-db thread adoption

 gdb/linux-nat.c                             |  25 +-
 gdb/linux-nat.h                             |   2 +-
 gdb/linux-thread-db.c                       |  67 +++--
 gdb/testsuite/gdb.threads/clone-bad-tls.c   | 193 +++++++++++++
 gdb/testsuite/gdb.threads/clone-bad-tls.exp | 294 ++++++++++++++++++++
 gdbserver/thread-db.cc                      |  14 +-
 6 files changed, 553 insertions(+), 42 deletions(-)
 create mode 100644 gdb/testsuite/gdb.threads/clone-bad-tls.c
 create mode 100644 gdb/testsuite/gdb.threads/clone-bad-tls.exp


base-commit: 9d3cf9efd51ebae3f45bb49e3544cb7eeb63a138
-- 
2.25.4


             reply	other threads:[~2026-04-07 10:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-07 10:22 Andrew Burgess [this message]
2026-04-07 10:22 ` [PATCH 1/3] gdb: int to bool conversion in linux-thread-db.c Andrew Burgess
2026-05-05 18:19   ` Keith Seitz
2026-04-07 10:22 ` [PATCH 2/3] gdb: add some asserts to thread_db_notice_clone Andrew Burgess
2026-05-05 18:24   ` Keith Seitz
2026-04-07 10:22 ` [PATCH 3/3] gdb: improve error handling for thread-db thread adoption Andrew Burgess
2026-05-06 19:39   ` Keith Seitz

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.1775557188.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