public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "rvansa at azul dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug threads/31568] New: GDB fails with raw clone syscalls
Date: Thu, 28 Mar 2024 14:19:14 +0000	[thread overview]
Message-ID: <bug-31568-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 31568
           Summary: GDB fails with raw clone syscalls
           Product: gdb
           Version: 12.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: threads
          Assignee: unassigned at sourceware dot org
          Reporter: rvansa at azul dot com
  Target Milestone: ---

I am trying to debug into CRIU (https://criu.org/), though I have seen this
problem in other instances where the clone/clone3 syscall is invoked directly.
When this is executed GDB prints

```
Cannot find user-level thread for LWP 341734: generic error
```

After this, `info thread` won't show the new thread. It is marked as being
traced (but I guess that all threads from traced process show that).
```
$ cat /proc/341519/task/341734/status
Name:   java
Umask:  0002
State:  t (tracing stop)
Tgid:   341519
Ngid:   0
Pid:    341734
PPid:   341503
TracerPid:      341503
...
```

I can switch back to the original thread using `thread 1` but is is marked as
running and I cannot interrupt it (neither using ctrl+C nor with signal
SIGINT).

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

                 reply	other threads:[~2024-03-28 14:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-31568-4717@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).