[patch] recognise when an exec()d process terminates due to unhandled exception

Christopher Faylor cgf-use-the-mailinglist-please@cygwin.com
Sun Mar 23 03:51:00 GMT 2008

On Fri, Mar 14, 2008 at 11:11:43PM -0700, Brian Dessent wrote:
>Christopher Faylor wrote:
>>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.
>The patch doesn't change any behavior though: in current Cygwin if the
>thing we're exec()ing returns a Win32 exit code of C0000135 (or
>whatever) then we retry creating it 5 times.  With the patch, we still
>retry starting it 5 times but after the last one fails we recognise the
>situation and print a message.

After poking at this a little, I think it would be better to issue a
linux-like error message.

In my sandbox, I now have this:

bash-3.2$ ./libtest
/cygdrive/s/test/libtest.exe: error while loading shared libraries: liba.dll: cannot open shared object file: No such file or directory

I haven't done the work to report on missing symbols yet but I think
that's a much less common error condition.

So thanks for the patch and the concept but I think I'd rather go with a
more linux-like solution.


More information about the Cygwin-patches mailing list