Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: gdb-patches@sources.redhat.com
Subject: [PATCH] linux-nat.c
Date: Thu, 14 Sep 2006 03:58:00 -0000	[thread overview]
Message-ID: <17672.53943.265838.195451@kahikatea.snap.net.nz> (raw)


On nickrob-async-20060513-branch I get a zombie process each time I start the
inferior.  It doesn't happen for me on mainline but the patch below seems to
belong there anyway.

-- 
Nick                                           http://www.inet.net.nz/~nickrob


2006-09-14  Nick Roberts  <nickrob@snap.net.nz>

	* linux-nat.c (linux_test_for_tracefork): Don't leave zombie process.

*** linux-nat.c	24 Jul 2006 09:21:01 +1200	1.49
--- linux-nat.c	14 Sep 2006 15:48:58 +1200	
***************
*** 276,281 ****
--- 276,282 ----
  	  ret = ptrace (PTRACE_KILL, second_pid, 0, 0);
  	  if (ret != 0)
  	    warning (_("linux_test_for_tracefork: failed to kill second child"));
+ 	  my_waitpid (second_pid, &status, 0);
  	}
      }
    else


             reply	other threads:[~2006-09-14  3:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-14  3:58 Nick Roberts [this message]
2006-09-16  4:03 ` Daniel Jacobowitz

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=17672.53943.265838.195451@kahikatea.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=gdb-patches@sources.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