This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: optimizing fork/exec in vendor source
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
According to Jack Andrews on 10/10/2008 7:50 PM:
> i'm naive when it comes to cygwin internals, but the obvious
> similarity of posix_spawn to CreateProcess is seductive. can you give
> me an example of one of the difficulties of implementing posix_spawn
> in cygwin so i don't bother the list anymore?
Exactly how do you propose to implement posix_spawnattr_setsigdefault
without understanding cygwin internals, and given the fact that native
Windows API is woefully lacking in sigset_t coding? Think about it -
since cygwin provides the illusion of more signals than Windows, and POSIX
requires the child process created by posix_spawn to change its signal
mask according to the POSIX_SPAWN_SETSIGDEF flag, that means that you must
create the child process in such a way that it knows the right set of
cygwin signal masks it is inheriting. If cgf says it's hard (and he's the
one that maintains signal and fork code), it's probably hard.
- --
Don't work too hard, make some time for fun as well!
Eric Blake ebb9@byu.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkjwHwkACgkQ84KuGfSFAYAJegCgtrFsk6fcCL5ZSyhUgCThYleJ
sbgAn0iUW/LqCMvttPIboBUhAWDfcZ5R
=2tpJ
-----END PGP SIGNATURE-----
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/