Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Fix crash on /proc/PID/stat race
Date: Thu, 27 May 2010 22:50:00 -0000	[thread overview]
Message-ID: <201005272325.40987.pedro@codesourcery.com> (raw)
In-Reply-To: <20100527212037.GA24735@host0.dyn.jankratochvil.net>

On Thursday 27 May 2010 22:20:37, Jan Kratochvil wrote:
> On Thu, 27 May 2010 21:00:26 +0200, Pedro Alves wrote:
> > Why are we trying to get at the core if we know the process
> > is gone?  Since the process is already waited for, I'm surprised
> > the fopen succeeded in the first place.  On a couple of quick tests,
> > I always see fopen failing.  It sounds like a kernel bug.  Can't we
> > just skip the core_of_thread call for
> > TARGET_WAITKING_EXITED|TARGET_WAITKING_SIGNALLED?
> 
> An additional patch like this one?

Yes, exactly.  Thanks.

> It is IMO not correct for GDB to crash on unexpected /proc/** content.

Okay, I don't mind your original patch that much.  I think that it
adds a bit of complexity by being paranoid.  As long as a process
hasn't been waited for, the /stat entry should exist, even if the
process is zombie.

Anyway, if you want to put that one in, it's okay, but please don't
lose the comment below:

> -  p = strchr (p, ')') + 2; /* skip ")" and a whitespace. */
> +  if (p != NULL)
> +    p = strchr (p, ')');

and I don't think the fopen race comment makes sense
as is anymore.

Also, IWBN if gdbserver was fixed similarly, but I won't ask
you to do that.  :-)

-- 
Pedro Alves


  reply	other threads:[~2010-05-27 22:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-27 18:00 Jan Kratochvil
2010-05-27 19:06 ` Pedro Alves
2010-05-27 21:24   ` Jan Kratochvil
2010-05-27 22:50     ` Pedro Alves [this message]
2010-05-28 18:28       ` Jan Kratochvil

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=201005272325.40987.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@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