Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com content-class: urn:content-classes:message Subject: RE: Alloc_sd() fragile? MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Date: Tue, 5 Mar 2002 23:26:43 +1100 X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Alloc_sd() fragile? Thread-Index: AcHEMgfU7/974SGrQQC4LvH9YGWuOwADrptA From: "Robert Collins" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g25CQrV27536 > -----Original Message----- > From: Corinna Vinschen [mailto:vinschen AT redhat DOT com] > Just guessing. One parameter to alloc_sd is a > PSECURITY_DESCRIPTOR called `sd_ret'. This SD must be > initialized since it's used as in/out parameter. Take a look > into set_security_attribute() and especially into > set_nt_attribute(). You will see what I mean. Thank you!, that was it. It wasn't my bug however :[, as the CreateFile is still failing, but the alloc_sd failures are gone (different sd's are used). *sigh*. Something is tromping on a static class member and invalidating the sd. Are sd's ever corrupted by system calls, or can one reuse an sd indefinately? Rob