Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] linux_nat_kill() compat. with linux-2.4.x
Date: Mon, 09 Jun 2014 10:32:00 -0000	[thread overview]
Message-ID: <20140609103245.GA29982@host2.jankratochvil.net> (raw)
In-Reply-To: <53958C88.4070209@redhat.com>

On Mon, 09 Jun 2014 12:29:28 +0200, Pedro Alves wrote:
> On 06/06/2014 09:15 PM, Jan Kratochvil wrote:
> > It also may hang somewhere else and not in linux_nat_kill().
> 
> Right.  I'd say it's much more likely (even though not very likely, tbc)
> that we see hangs elsewhere than in linux_nat_kill now.  E.g., GDB core's
> is_executing state getting out of sync with lwp->stopped.
> 
> > This patch made GDB foolproof against any state of inferior when killing the
> > inferior so that GDB could no longer hang.  But it would hide some possible
> > remaining bugs in the code (which may be causing the GDB hangs).
> 
> Right, I'd rather just fix the GDB bugs, and only consider such a patch
> if we need to work around a kernel bug (though I'd rather just
> ignore very old kernels like 2.4 by now).

OK, so according to the approach chosen above considering this patch dropped.


Jan


      reply	other threads:[~2014-06-09 10:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-16 13:59 Jan Kratochvil
2014-05-21 12:49 ` Pedro Alves
2014-06-06 20:15   ` Jan Kratochvil
2014-06-09 10:29     ` Pedro Alves
2014-06-09 10:32       ` Jan Kratochvil [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=20140609103245.GA29982@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@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