Mailing-List:	contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-developers/>
List-Post:	<mailto:cygwin-developers AT cygwin DOT com>
List-Help:	<mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-developers-owner AT cygwin DOT com
Delivered-To:	mailing list cygwin-developers AT cygwin DOT com
Date:	Tue, 12 Nov 2002 09:58:48 -0500
From:	Jason Tishler <jason AT tishler DOT net>
Subject:	Re: dll_list::detach() can stackdump
In-reply-to:	<20021107171831.GA1752@tishler.net>
To:	Cygwin-Developers <cygwin-developers AT cygwin DOT com>
Mail-followup-to:	Cygwin-Developers <cygwin-developers AT cygwin DOT com>
Message-id:	<20021112145848.GF792@tishler.net>
MIME-version:	1.0
User-Agent:	Mutt/1.4i
References:	<20021107171831 DOT GA1752 AT tishler DOT net>

On Thu, Nov 07, 2002 at 12:18:31PM -0500, Jason Tishler wrote:
> I'm trying to debug a dll_list::detach() stackdump problem that I
> first triggered by a Cygwin Perl application.  Specifically, the
> problem occurs at the following dll_init.cc line:
> 
>     void
>     dll_list::detach (dll *d)
>     {
>         ...
> ***>    if (d->count <= 0)
>         ...
>     }

Although, the following patch:

    http://cygwin.com/ml/cygwin-patches/2002-q4/msg00103.html

fixes the problem for newly built DLLs, it does not (and cannot) correct
old (i.e., previously built) DLLs.

What is the best way to solve this issue?  Should dll_list::detach() be
changed to call IsBadReadPtr() to prevent stackdumps?

Thanks,
Jason

-- 
PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers
Fingerprint: 7A73 1405 7F2B E669 C19D  8784 1AFD E4CC ECF4 8EF6

- Raw text -