X-Recipient: archive-cygwin@delorie.com
X-SWARE-Spam-Status: No, hits=-3.5 required=5.0 	tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_PASS,UNPARSEABLE_RELAY
X-Spam-Check-By: sourceware.org
To: cygwin@cygwin.com
From: Eric Blake <ebb9@byu.net>
Subject:  Re: [1.7] old-style symlink handle leak
Date: Wed, 24 Dec 2008 17:35:01 +0000 (UTC)
Lines: 24
Message-ID:  <loom.20081224T172538-538@post.gmane.org>
References:  <loom.20081224T152703-183@post.gmane.org> <20081224163623.GA15747@ednor.casa.cgf.cx>
Mime-Version:  1.0
Content-Type:  text/plain; charset=us-ascii
Content-Transfer-Encoding:  7bit
User-Agent: Loom/3.14 (http://gmane.org/)
X-IsSubscribed: yes
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

Christopher Faylor <cgf-use-the-mailinglist-please <at> cygwin.com> writes:

> I'm building a snapshot now.  If you are in a position of being able to
> test this when it finally shows up I'd appreciate hearing if my changes
> fixes the problem.

Yep, when I used your snapshot, a search for the substring .lnk in process 
explorer no longer turns up anything, so it looks like you fixed the leak.

But when I tried a self-built dll, I'm getting a stackdump when rxvt exits:

c:\cygwin-2\bin> rxvt
1505750 [proc_waiter] rxvt 8684 _cygtls::handle_exceptions: Exception: 
STATUS_ACCESS_VIOLATION
1506088 [proc_waiter] rxvt 8684 open_stackdumpfile: Dumping stack trace to 
rxvt.exe.stackdump

I'm not sure if it is something I've changed locally, so now I'm working on 
narrowing that down to see why my self-built image isn't behaving like your 
snapshot.

-- 
Eric Blake



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