Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Wed, 11 Feb 2004 12:24:58 -0500
From: "Pierre A. Humblet" <pierre DOT humblet AT ieee DOT org>
To: cygwin AT cygwin DOT com
Subject: Re: 1.5.7: core sump: ls /proc/registry
Message-ID: <20040211172458.GA95925@Worldnet>
References: <Xns948C6CEA7CD3Echuckhsofthomenet AT 80 DOT 91 DOT 224 DOT 252> <20040211162659 DOT GA16399 AT redhat DOT com> <20040211163251 DOT GA95821 AT Worldnet> <20040211172411 DOT GY4162 AT cygbert DOT vinschen DOT de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040211172411.GY4162@cygbert.vinschen.de>
User-Agent: Mutt/1.4.1i

On Wed, Feb 11, 2004 at 06:24:11PM +0100, Corinna Vinschen wrote:
> On Feb 11 11:32, Pierre A. Humblet wrote:
> > On Wed, Feb 11, 2004 at 11:26:59AM -0500, Christopher Faylor wrote:
> > > On Wed, Feb 11, 2004 at 03:42:24PM +0000, Chuck wrote:
> > > >I just upgraded to 1.5.7. When I do "ls /proc/registry" I get a core 
> > > >dump. 
> > > >
> > > >$ ls /proc/registry
> > > >Segmentation fault (core dumped)
> > > 
> > > "Works for me"
> > 
> > /bin/ls /proc/registry works for me too but
> > /bin/ls -F /proc/registry fails.
> 
> Something's going wrong in get_nt_object_attribute.

Right.
Problem happens with non-existant
/proc/registry/HKEY_PERFOMANCE_DATA

It's surely useless to call sd.malloc (len)
when the first call to RegGetKeySecurity has failed.

Pierre



--
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/