public inbox for archer@sourceware.org
 help / color / mirror / Atom feed
From: Roland McGrath <roland@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Oleg Nesterov <oleg@redhat.com>, archer@sourceware.org
Subject: Re: [patch] Re: [BUG] gdb: quit hangs after step into signal handler
Date: Wed, 23 Feb 2011 20:27:00 -0000	[thread overview]
Message-ID: <20110223202710.6B8AE1800B4@magilla.sf.frob.com> (raw)
In-Reply-To: Jan Kratochvil's message of  Wednesday, 23 February 2011 21:24:54 +0100 <20110223202454.GA4687@host1.dyn.jankratochvil.net>

> On Wed, 22 Sep 2010 01:53:56 +0200, Roland McGrath wrote:
> > 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.
> 
> Problem is the inferior will start running after PTRACE_KILL.  Current GDB:
> 
> Quit anyway? (y or n) y
> <hang by sleep (600);>
> 
> read(0, "y\n", 1024)                    = 2
> ptrace(PTRACE_KILL, 32336, 0, 0)        = 0
> wait4(32336,
> 
> Before kill (SIGKILL) gets applied the code may do something unexpected.
> Why do you consider SIGKILL first, PTRACE_KILL second as worse?

What I recommended is kill/SIGKILL first, PTRACE_KILL second.  
That's not worse than anything else.

      reply	other threads:[~2011-02-23 20:27 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
2011-02-23 20:25   ` [patch] " Jan Kratochvil
2011-02-23 20:27     ` Roland McGrath [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=20110223202710.6B8AE1800B4@magilla.sf.frob.com \
    --to=roland@redhat.com \
    --cc=archer@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --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).