public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "pedro at palves dot net" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug threads/31579] Cannot find user-level thread for LWP
Date: Thu, 11 Apr 2024 12:00:29 +0000	[thread overview]
Message-ID: <bug-31579-4717-QZWnx92s7T@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31579-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=31579

--- Comment #3 from Pedro Alves <pedro at palves dot net> ---
BTW, for completeness, you don't need fork to trigger this.  All you need is to
set a breakpoint that is hit by any thread other than the leader.  E.g., using
the same test program:

(gdb) b thread
Breakpoint 1 at 0x11b9: file forking.c, line 6.
(gdb) r
Starting program: /tmp/forking
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffff7bff640 (LWP 3266257)]
Cannot find user-level thread for LWP 3266257: generic error

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2024-04-11 12:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-29 20:11 [Bug threads/31579] New: " ssbssa at sourceware dot org
2024-03-29 20:15 ` [Bug threads/31579] " ssbssa at sourceware dot org
2024-03-31 12:22 ` ssbssa at sourceware dot org
2024-04-11 11:41 ` pedro at palves dot net
2024-04-11 12:00 ` pedro at palves dot net [this message]
2024-04-26 21:02 ` cvs-commit at gcc dot gnu.org
2024-05-03 16:27 ` pedro at palves dot net
2024-05-03 16:28 ` pedro at palves dot net

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=bug-31579-4717-QZWnx92s7T@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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).