X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:subject:message-id:reply-to :references:mime-version:content-type:in-reply-to; q=dns; s= default; b=OvJuerpMQXVeDFjEJ4Rvs0EF4zIK7xVs7E2WLgP43+hVNaAuSPrBP 2RGW5emSbMgsQ8W6Djeo+Q8IItS8aBQSUj9hgqBgA5+oVeUJ4P1RlsIwa+Dc50YX ISWJVDAWGyhiGAJY7PtSjNjEhgZ+mLusmmLLTuRWAXrzdxn2TqN+OY= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:subject:message-id:reply-to :references:mime-version:content-type:in-reply-to; s=default; bh=7G+3yfJ7ac7Hug6bLiY1THJzgWY=; b=OVEzDhvRX6bzR7AK0autrnh7LZU/ OZxBchUUDwREeH7eToezVEaBU9UL7cgpeG9vyMDdTrW1TiNZZ10RJG1BPIuy/qUn Zt+RHXbGTQOVNWfPrEtYTZhfi7CCHd/tzq7bRLvPCeHhMYEelUMo3x3PZ5NqyGit KpKmPkw/m4PHlzo= 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 X-Spam-SWARE-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.1 Date: Mon, 27 May 2013 19:07:23 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: STC for fork SEGV after dlclose Message-ID: <20130527170723.GF28463@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <51A38C2B DOT 6060706 AT acm DOT org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <51A38C2B.6060706@acm.org> User-Agent: Mutt/1.5.21 (2010-09-15) On May 27 09:39, David Rothenberger wrote: > The libapr1 test cases starting failing with my 64-bit package and > 1.7.19-6. They worked fine with 1.7.19-5. After a little > investigation, I discovered that only the tests that involve fork() > were failing and only if the "testdso" test case ran first. That > test case checks loading and unloading DLLs. Sigh. Thanks for the testcase. I wonder if it wouldn't be easier to drop libapr1 instead... ;} > I extracted the attached STC. It creates a simple DLL and uses > dlopen() and dlclose() on it. Then it attempts a fork(). > > With the latest 32-bit snapshot (2013-05-24) this causes a > segfault. The same thing happens with the 64-bit release. With > 1.7.18, the test case hangs for quite a while, but eventually > finishes, except that the fork() never really happens and I get a > weird error code when I run it in gdb. If I skip the dlclose() call, > the STC runs fine. > > It's weird, but the libapr1 test suite does not fail on 32-bit with > the 2013-05-24 snapshot (or with 1.7.18). I don't know why the STC ^^^^^^^^^^ ???? Above you said it fails on 32 bit with 2013-05-24, too. What's the last working snapshot? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple