This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: kill(pid, 0) issue

On Wed, Dec 17, 2003 at 05:23:20PM +0100, Nowakowski Maciej-AMN011 wrote:
>My application creates additional process using fork() function.
>Created child process listens on a socket and exits when it receives
>anything.  The main process checks the child PID using kill(pid, 0)
>with child PID as a parameter.  Even when the child has exited this
>function call returns 0.  When I have supplied any PID which hasn't
>ever existed it's fine and kill(non-existentPID, 0) returns -1.
>Has anyone experienced something like this?

This seems like a perfect place for a simple test case.  For instance:

#include <stdio.h>
#include <stdlib.h>
#include <signal.h>
#include <unistd.h>
#include <sys/wait.h>

main (int argc, char **argv)
  int pid;
  if (argv[1])
    pid = atoi(argv[1]);
  else if ((pid = fork ()) == 0)
      puts ("forking a process and then exiting");
      exit (0);
      int dummy;
      wait (&dummy);
  printf ("%d = kill (%d, 0)\n", kill (pid, 0), pid);
  exit (0);

I tried the above with no argument and with an argument of a previously
forked-and-exited process.  Both cases produced the expected result, as
did trying this on a running process.

I suspect that you are not 'wait()'ing for the process to exit before
checking if it exists.  kill(pid, 0) will succeed on both linux and cygwin
if the process is not reaped by calling wait (or waitpid, etc.) first.


Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]