DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=Wlhxf6s7G/vf8BvbHuHwLlKRmEcSZIxedsoCW6tEkYe
	ZqE110b0WntXu3ksf+Vt/SUibE+fb6q1MCzXAZBdAA+l4k64TFXmEe51/M/M0hR9
	U+tBpEm4FclO4TOLzskQKMi+5OrWb5NS/d47fxjWxKk5V7ADYM7SRDdeIXIdKBDw
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <53C51460.5080805@cornell.edu>
Date: Tue, 15 Jul 2014 07:45:36 -0400
From: Ken Brown <kbrown@cornell.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: Core dump on 32-bit Cygwin if program calls dlopen
References: <53C46ACD.5060601@cornell.edu> <20140715090259.GB20640@calimero.vinschen.de>
In-Reply-To: <20140715090259.GB20640@calimero.vinschen.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 7/15/2014 5:02 AM, Corinna Vinschen wrote:
> On Jul 14 19:42, Ken Brown wrote:
>> I'm getting a core dump on exit from a program that does nothing but call
>> dlopen.  (But the call to dlopen succeeds.)  This happens only in the 32-bit
>> case.  Here's a simple test case.
>>
>> $ cat test_dlopen.c
>> #include <stdio.h>
>> #include <dlfcn.h>
>> int
>> main()
>> {
>>    const char *dllname = "cyggs-9.dll";
>>    void *handle;
>>    printf ("Trying to dlopen %s...", dllname);
>>    handle = dlopen (dllname, RTLD_LAZY);
>>    if (handle)
>>      {
>>        printf ("succeeded.\n");
>>        return 0;
>>      }
>>    else
>>      {
>>        printf ("failed.\n");
>>        return 1;
>>      }
>> }
>>
>> $ gcc test_dlopen.c
>>
>> $ ./a
>> Trying to dlopen cyggs-9.dll...succeeded.
>> Aborted (core dumped)
>
> The crash occurs when calling the destructors from do_global_dtors.
> The crash address points to a crash inside a destructor of libgcc
> (actually cyggcc_1-1.dll) which has been pulled in by cyggs-9.dll.
>
> What destructor in libgcc would that be?  And what is it expecting
> which is apparently missing?

FWIW, the problem disappears if I revert gcc-core and libgcc1 to 4.8.2-2.

Ken

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