Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-ID: <D721826DEE793D49BC49582C121EDD3E7FC6@exchange.perwill.com>
From: Steve Fairbairn <steve DOT fairbairn AT perwill DOT com>
To: "'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
Subject: FW: Problem with Cygwin DLL: 1003.15.0.0 & 1003.16.0.0
Date: Thu, 28 Nov 2002 11:46:50 -0000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Note-from-DJ: This may be spam


Hi all,

As noone responded to this, and I have since seen minor complaints of not
enough information being given, is there anything further I can do to assist
in the location and repair of this problem?

I have upgraded to 1003.17.0.0 and ensured the problem is also in this
version of the dll.  Do I have to reboot after upgrade, if the dll has been
changed (Win2K)?

Thanks,

Steve.

-----Original Message-----
From: Steve Fairbairn [mailto:steve DOT fairbairn AT perwill DOT com]
Sent: 25 November 2002 13:07
To: 'cygwin AT cygwin DOT com'
Subject: Problem with Cygwin DLL: 1003.15.0.0 & 1003.16.0.0


Hi,

I have come across a problem with cygwin which relates to the Windows
CreateProcess() function.

Tested on 
Cygwin DLLs: 1003.15.0.0 & 1003.16.0.0
Windows 2000 sp3

I have a Visual C++ program which uses CreateProcess to launch an executable
much like the example provided in the attachment.  The example has been hard
coded to execute a cygwin compiled binary (ls) as this is what I was
attempting to do in the real thing.

When the program is run from a dos command prompt, it all works perfectly.
However when the program is run from cygwin bash, the launched program (ls)
fails with a read exception somewhere in the cygwin dll.

If the program is changed to execute a non cygwin-built binary, it all seems
to work fine.

I also bring your attention to the following lines from the example...

    /* Something to do with bInheritHandles being FALSE, as when it is TRUE,
it works. */
    CreateProcess(0, cmd, 0, 0, FALSE,
                        DETACHED_PROCESS | NORMAL_PRIORITY_CLASS,
                        0,
                        cwd,
                        &StartupInfo,
                        &ProcessInformation);

When the CreateProcess call is changed so handles are inherited, it all
works perfectly.

If this is the wrong place to report an issue like this, then please let me
know where I should email instead.  I couldn't spot any other likely
candidates.

Regards,

Steve Fairbairn.

 <<test.c>> 
PS. Full VC++ Workspace and binaries are available, I just didn't want to
attach it on a mail to the whole list.
PPS. Apologies for the disclaimer, nothing I can do to stop it :(.

-- 
^^ Vain attempt to fake a proper signature start so hopefully some people
will automatically trim it off.

******************************************************* 
This email has originated from Perwill plc (Registration No. 1906964) 
Office registered at: 13A Market Square, Alton, Hampshire, GU34 1UR, UK 
Tel: +44 (0)1420 545000 
Fax: +44 (0)1420 545001 
www.perwill.com 
******************************************************* 
Privileged, confidential and/or copyright information may be contained 
in this email, and is only for the use of the intended addressee. 
To copy, forward, disclose or otherwise use it in any way if you are not 
the intended recipient or responsible for delivering to him/her is
prohibited.
If you receive this email by mistake, please advise the sender immediately, 
by using the reply facility in your email software.

We may monitor the content of emails sent and received via our network 
for the purposes of ensuring compliance with policies and procedures. 
This message is subject to and does not create or vary any contractual 
relationships between Perwill plc and the recipient. 
******************************************************* 
Any opinions expressed in the email are those of the sender and not 
necessarily of Perwill plc.
******************************************************* 
This email has been scanned for known viruses using 
McAfee WebShield 4.5 MR1a 
******************************************************* 


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/