X-Recipient: archive-cygwin AT delorie DOT 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 AT cygwin DOT com From: Eric Blake Subject: Re: [1.7] old-style symlink handle leak Date: Wed, 24 Dec 2008 17:35:01 +0000 (UTC) Lines: 24 Message-ID: References: <20081224163623 DOT GA15747 AT ednor DOT casa DOT cgf DOT 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 AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Christopher Faylor 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/