This is the mail archive of the cygwin-patches mailing list for the Cygwin project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

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: Fri, 14 Mar 2008 23:11:43 -0700
Subject: Re: [patch] recognise when an exec()d process terminates due to unhandled exception
References: <47D9D8D3.17BC1E3B@dessent.net> <47D9E70D.ED6C84CB@dessent.net> <20080314141331.GB20808@ednor.casa.cgf.cx>
Reply-to: cygwin-patches at cygwin dot com

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.

Brian

Follow-Ups:
- Re: [patch] recognise when an exec()d process terminates due to unhandled exception
  - From: Christopher Faylor

References:
- [patch] recognise when an exec()d process terminates due to unhandled exception
  - From: Brian Dessent
- Re: [patch] recognise when an exec()d process terminates due to unhandled exception
  - From: Brian Dessent
- Re: [patch] recognise when an exec()d process terminates due to unhandled exception
  - From: Christopher Faylor

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]