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: Brian Dessent <brian at dessent dot net>
- To: cygwin-patches at cygwin dot com
- Date: Thu, 13 Mar 2008 19:46:37 -0700
- Subject: Re: [patch] recognise when an exec()d process terminates due to unhandled exception
- References: <47D9D8D3.17BC1E3B@dessent.net>
- Reply-to: cygwin-patches at cygwin dot com
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. I had at one point a testcase so
pathological that it somehow managed to invoke a MS runtime popup error,
even though it was a pure Cygwin binary. And you'd get 5 copies of the
thing before it gave up and stopped trying. You can see it in strace a
lot easier though since strace is running the debugger loop you see the
exceptions.
Brian