public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "xdje42 at gmail dot com" <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: Mon, 14 Sep 2015 16:45:00 -0000	[thread overview]
Message-ID: <bug-18945-4717-TqqpeSXRDZ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18945-4717@http.sourceware.org/bugzilla/>

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

Doug Evans <xdje42 at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |xdje42 at gmail dot com

--- Comment #1 from Doug Evans <xdje42 at gmail dot com> ---
A description of why things are the way they are can be found in the commit
message of commit 78708b7c8ccc2138880217de9bd60eceff683f10.

Basically, the main thread could have exited, in which case sending a signal
just to it will be a no-op.

Signals can be sent across process groups, are you sure that's the problem?

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


  parent reply	other threads:[~2015-09-14 16:45 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 [this message]
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

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-TqqpeSXRDZ@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).