X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org From: "Dave Korn" To: References: <47D4A7E4 DOT 5070509 AT tlinx DOT org> <47D4B7D2 DOT 1F78DADB AT dessent DOT net> <47D4E892 DOT 1090305 AT tlinx DOT org> <47D50BB6 DOT EFB28302 AT dessent DOT net> <47D6056B DOT 6000805 AT tlinx DOT org> <47D610C2 DOT EECE7EE9 AT dessent DOT net> Subject: RE: Bug: C-prog from Win dies in fork; gdb.exe also won't run Date: Wed, 12 Mar 2008 12:16:00 -0000 Message-ID: <00b601c8843a$d94fe2c0$2708a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <47D610C2.EECE7EE9@dessent.net> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Brian Dessent wrote on 11 March 2008 04:56: > - When the testcase's binary is located anywhere but %windir% or > %windir%\system32, then everything is fine. > - Otherwise you get: Ah. So the error only arises when the binary is located in windows system dir. Right alongside all those thousands of DLLs. All those DLLs which are now all of a sudden higher up in the DLL search path than they were when the binary was located somewhere else. Just a WAG, but that could be significant. > > I hear what you are saying...yet did you know that MS > > improved fork and exec performance by 30% in their SFU Unix-compat > > layer? :-). I wonder what 'pains' they go through -- they might have it > > easier and just use straight NT calls rather than Win32. Dunno... > > They don't go to any pains. The sad part is that the NT kernel does > support fork semantics. But it only exposes them to the Posix > subsystem, which is what SFU runs in. It doesn't expose them to the > Win32 subsystem. The native API, to the very best of my knowledge, exports exactly the same set of interfaces to every subsystem. Can you explain exactly what you're talking about here? cheers, DaveK -- Can't think of a witty .sigline today.... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/