Date: Thu, 16 Sep 2004 19:31:22 -0400 (EDT) From: Daniel Eischen <deischen@freebsd.org> To: David Xu <davidxu@freebsd.org> Cc: freebsd-threads@freebsd.org Subject: Re: SIGILL @ pthread_create() after execv -FIXED- Message-ID: <Pine.GSO.4.43.0409161929250.26414-100000@sea.ntplx.net> In-Reply-To: <414A20F9.5000304@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 17 Sep 2004, David Xu wrote: > Daniel Eischen wrote: > > >We do that in fork(). Is execv() not being done after a fork()? > > > > > > > Joost calls execv() directly in threaded process, he did not go through > fork() ->execv() path. Yes, Julian just emailed me similarly. In that case, I think we need to wrap execve() and set the kernel signal mask to the threads signal mask. We don't need all the single threading stuff that is in our wrapped fork(); just __sys_sigprocmask() should be sufficient. Right? -- Dan Eischen
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.43.0409161929250.26414-100000>