Re: [PATCH v2 0/2] silent fork retry with shm (broke emacs-X11)

On 7/31/2019 12:59 PM, Corinna Vinschen wrote: > On Jul 31 12:35, Michael Haubenwallner wrote: >> Hi Corinna, >> >> On 7/30/19 6:07 PM, Corinna Vinschen wrote: >>> Hi Michael, >>> >>> On Jul 30 17:22, Michael Haubenwallner wrote: Hi, following up

Re: [PATCH v2 0/2] silent fork retry with shm (broke emacs-X11)

On Jul 31 12:35, Michael Haubenwallner wrote: > Hi Corinna, > > On 7/30/19 6:07 PM, Corinna Vinschen wrote: > > Hi Michael, > > > > On Jul 30 17:22, Michael Haubenwallner wrote: > >> Hi, > >> > >> following up > >> https://cygwin.com/ml/cygwin-patches/2019-q2/msg00155.html > >> > >> It turns out

[PATCH v2 2/2] Cygwin: fork: attach child not before success

Do not attach to the child before it was successfully initialized, or we would need more sophisticated cleanup on child initialization failure, like suppressing SIGCHILD delivery with multiple threads ("waitproc") involved. Improves "Cygwin: fork: Remember child not before success.", commit

[PATCH v2 1/2] Cygwin: pinfo: stop remember doing reattach

During fork, the child process requires the process table to be initialized for fixup_shms_after_fork, while still allowing subsequent dlls.load_after_fork to fail silently (for when the "forkable" hardlinks are not created yet). pinfo::remember not performing reattach anymore requires explicit

[PATCH v2 0/2] silent fork retry with shm (broke emacs-X11)

Hi Corinna, On 7/30/19 6:07 PM, Corinna Vinschen wrote: > Hi Michael, > > On Jul 30 17:22, Michael Haubenwallner wrote: >> Hi, >> >> following up >> https://cygwin.com/ml/cygwin-patches/2019-q2/msg00155.html >> >> It turns out that fixup_shms_after_fork does require the child pinfo to >> be