public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "thiago at kde dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/26562] gdb follows both sides of a clone2(CLONE_PIDFD) on Linux >= 5.4 Date: Thu, 17 Sep 2020 20:26:13 +0000 [thread overview] Message-ID: <bug-26562-4717-ezRPYPH3NP@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-26562-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=26562 Thiago Macieira <thiago at kde dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #1 from Thiago Macieira <thiago at kde dot org> --- Update: looks like the issue is that the code is not passing SIGCHLD as the termination signal to clone(), which causes the kernel to send PTRACE_EVENT_CLONE instead of PTRACE_EVENT_FORK. That confuses gdb. Changing the clone code fixed the problem. It's still technically a bug in gdb, but not worth fixing. -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2020-09-17 20:26 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-01 15:36 [Bug gdb/26562] New: " thiago at kde dot org 2020-09-17 20:26 ` thiago at kde dot org [this message]
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-26562-4717-ezRPYPH3NP@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: linkBe 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).