This is the mail archive of the
mailing list for the Cygwin project.
Re: STC for fork SEGV after dlclose
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Mon, 27 May 2013 19:07:23 +0200
- Subject: Re: STC for fork SEGV after dlclose
- References: <51A38C2B dot 6060706 at acm dot org>
- Reply-to: cygwin at cygwin dot com
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 Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple