public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/18945] gdbserver cannot be interrupted on linux when pgid doesn't match pid Date: Tue, 11 Jul 2023 20:49:52 +0000 [thread overview] Message-ID: <bug-18945-4717-H3aKK6TwxV@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-18945-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=18945 Tom Tromey <tromey at sourceware dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tromey at sourceware dot org --- Comment #14 from Tom Tromey <tromey at sourceware dot org> --- It's not clear to me that removing the sign is the real fix. Like, it might work for your particular case, but regress some other case. There's a bunch of related bugs, at least bug#18772, bug#26575 as well as bug#23382 and bug#23621. -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2023-07-11 20:49 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-09-09 23:28 [Bug gdb/18945] New: " jmgao at google dot com 2015-09-14 16:45 ` [Bug gdb/18945] " xdje42 at gmail dot com 2015-09-14 16:45 ` xdje42 at gmail dot com 2015-09-14 17:29 ` jmgao at google dot com 2015-09-15 1:25 ` xdje42 at gmail dot com 2015-09-15 1:33 ` jmgao at google dot com 2015-09-15 1:52 ` xdje42 at gmail dot com 2015-09-15 2:02 ` xdje42 at gmail dot com 2015-09-16 21:53 ` jmgao at google dot com 2015-10-27 16:40 ` rarul at rarul dot com 2022-11-27 16:32 ` raj.khem at gmail dot com 2022-11-27 16:34 ` raj.khem at gmail dot com 2022-11-27 16:59 ` vries at gcc dot gnu.org 2023-06-29 8:45 ` prosup at 163 dot com 2023-07-11 20:49 ` tromey at sourceware 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-18945-4717-H3aKK6TwxV@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).