Re: vfork() question

[Andrey Repin <anrdaemon@yandex.ru>]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 1037 bytes --]

Greetings, Bence Szépkúti!

> Hello,

> I was poking around in the fork() code in Cygwin, and was wondering if
> someone could explain to me / point me to a discussion of why the NEWVFORK
> code was abandoned.

> I realise that this code had been disabled as "not working" since 2008,
> however I am interested in why this was the case. Was the concept behind
> "short-circuiting" vfork itself unfeasible in the context of Cygwin? Was a
> compatible implementation too complex / too slow to be worth it compared to
> a regular fork?

> Any insight is appreciated.

I could be wrong, but it may be due to a more reliable ways to implement
forking that became available in Win7+.


-- 
With best regards,
Andrey Repin
Saturday, July 27, 2019 13:34:49

Sorry for my terrible english...\x03B‹KCB”\x1c›Ø›\x19[H\x1c™\^[ܝ\x1cΈ\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÜ\x1c›Ø›\x19[\Ëš\x1d^[[\x03B‘TNˆ\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÙ˜\KÃB‘^[ØÝ[Y[\x18]\x1a[ÛŽˆ\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÙ^[ØÜËš\x1d^[[\x03B•[œÝXœØÜšX™H\x1a[™›Îˆ\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÛ[\vÈÝ[œÝXœØÜšX™K\Ú[\^[\x19CBƒB