Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Tue, 13 Mar 2001 01:05:53 -0500
From: Jason Tishler <Jason DOT Tishler AT dothill DOT com>
To: Cygwin <cygwin AT sources DOT redhat DOT com>
Subject: Why do DLLs require executable permission with ntsec?
Message-ID: <20010313010553.D1084@dothill.com>
Mail-Followup-To: Cygwin <cygwin AT sources DOT redhat DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
Organization: Dot Hill Systems Corp.

In trying to track down a Cygwin Python problem related to ntsec,
I first realized that DLLs seem to require executable permission when
ntsec is enabled.  Otherwise, the application which is dependent on the
DLL will fail to start with the following error dialog:

foo.exe - Application Error

The application failed to initialize properly (0xc0000022). Click on OK to
terminate the application.

Is this behavior by design?  I naively assumed that Windows would be
loading the DLL so Cygwin permissions would be irrelevant.  Can someone
please set me straight?

Thanks,
Jason

-- 
Jason Tishler
Director, Software Engineering       Phone: +1 (732) 264-8770 x235
Dot Hill Systems Corp.               Fax:   +1 (732) 264-8798
82 Bethany Road, Suite 7             Email: Jason DOT Tishler AT dothill DOT com
Hazlet, NJ 07730 USA                 WWW:   http://www.dothill.com

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple