public inbox for archer@sourceware.org
 help / color / mirror / Atom feed
From: Roland McGrath <roland@redhat.com>
To: Oleg Nesterov <oleg@redhat.com>
Cc: archer@sourceware.org
Subject: Re: [BUG] gdb: quit hangs after step into signal handler
Date: Tue, 21 Sep 2010 23:54:00 -0000	[thread overview]
Message-ID: <20100921235356.BB1F340614@magilla.sf.frob.com> (raw)
In-Reply-To: Oleg Nesterov's message of  Monday, 20 September 2010 23:17:15 +0200 <20100920211715.GA10574@redhat.com>

> Probably gdb should just do kill(tracee, SIGKILL) when it wants
> to terminate the tracee.

That's what I recommend.  (You only need one SIGKILL per process, not one
for each thread.  But if you still support linuxthreads, that will probably
need one for each thread.)  Even if you were paranoid about some old kernel
where PTRACE_KILL might work better (dubious if there are any such, but
that's why it's paranoia), you could do this before PTRACE_KILL and it
should certainly be fine everywhere.


Thanks,
Roland

  reply	other threads:[~2010-09-21 23:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-20 21:20 Oleg Nesterov
2010-09-21 23:54 ` Roland McGrath [this message]
2011-02-23 20:25   ` [patch] " Jan Kratochvil
2011-02-23 20:27     ` Roland McGrath

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=20100921235356.BB1F340614@magilla.sf.frob.com \
    --to=roland@redhat.com \
    --cc=archer@sourceware.org \
    --cc=oleg@redhat.com \
    /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).