Date: Sat, 11 Jan 2003 21:35:35 +0100 From: rmkml <rmkml@wanadoo.fr> To: Ferruccio Vitale <ferruccio.vitale@tin.it> Cc: hackers@FreeBSD.org Subject: Re: vfork/execve programming trouble Message-ID: <3E208017.F404526F@wanadoo.fr> References: <3E1608CB.E8BCCA90@wanadoo.fr> <20030110112641.1ebf0a5e.ferruccio.vitale@tin.it>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, Do you have the same pbs, or can't you reproduce the same blocking ? In my program, I use execve, In your program, you use execv, Do you think can make a difference ? Why do you catch a SIGCHLD in sig_thread too waitpid, and you waitpid too in exec_thread ? Why do you use waitpid twice ? Thanks a lot. Regards Ferruccio Vitale wrote: > Hi, > > I tried to reproduce your problem and, after a lot of effort, I think I found something interesting (take a look at code attached). > Regards, > > Ferruccio > > Note: SIGCHLD will never reach signal thread!! I think that waitpid locks this signal. > > ------------------------------------------------------------------------ > Name: prova3.c > prova3.c Type: unspecified type (application/octet-stream) > Encoding: base64 > > Part 1.2Type: application/pgp-signature To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3E208017.F404526F>