This is the mail archive of the
cygwin-patches
mailing list for the Cygwin project.
Re: [patch] recognise when an exec()d process terminates due to unhandled exception
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin-patches at cygwin dot com
- Date: Fri, 14 Mar 2008 10:13:31 -0400
- Subject: Re: [patch] recognise when an exec()d process terminates due to unhandled exception
- References: <47D9D8D3.17BC1E3B@dessent.net> <47D9E70D.ED6C84CB@dessent.net>
- Reply-to: cygwin-patches at cygwin dot com
On Thu, Mar 13, 2008 at 07:46:37PM -0700, Brian Dessent wrote:
>Brian Dessent wrote:
>
>> As we all know, Cygwin calls SetErrorMode (SEM_FAILCRITICALERRORS) to
>> suppress those pop up GUI messageboxes from the operating system when
>
>Oh, I forgot to mention:
>
>In the course of testing this I came to realize that because of some
>sort of "retry if fork doesn't seem to be working" code (not sure of the
>details), every time that this situation comes up we are actually
>launching five copies of the binary.
That was going to be my first observation, actually. I'm still trying
to digest the patch but it seems like it wouldn't work well with the
fork retry code.
cgf