Message332237
> I'm open to experiment to use vfork() in _posixsubprocess
Are you going to do experiments? If not, I can try to do some in early January.
> Using vfork() can cause new issues: that's why there is a POSIX_SPAWN_USE_VFORK flag (the caller had to explicitly enable it). See also bpo-34663 the history of vfork in posix_spawn() in the glibc.
I've studied that, and that's what I referred to as "quality-of-implementation" problem. After glibc devs removed heap allocations and tweaked some other things, they could use vfork() in all cases. "musl" libc never had those problems and used vfork() from the beginning. |
|
Date |
User |
Action |
Args |
2018-12-20 16:30:48 | izbyshev | set | recipients:
+ izbyshev, gregory.p.smith, pitrou, vstinner, serhiy.storchaka, pablogsal, nanjekyejoannah |
2018-12-20 16:30:47 | izbyshev | set | messageid: <1545323447.83.0.788709270274.issue35537@psf.upfronthosting.co.za> |
2018-12-20 16:30:47 | izbyshev | link | issue35537 messages |
2018-12-20 16:30:46 | izbyshev | create | |
|