delorie.com/archives/browse.cgi | search |
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=oG/44W8S+1o0QXFUEuXmLEB94ynbJq5kKzs3UI+j5WxXh7r8W2AuU | |
8DEjjchQPe61ZG/JJJ85/uF33JaJuN/27NwbKPYp7Sn7yhoguCEFo0m5jMYcMpoi | |
UJ4D9/tFWtkeseVEfQeMCaWIOJsHTCdh4xOkanOMHBXI1yr4b+D8Vc= | |
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=0MLaqI1h0RnjWhkM7FuOwWsdxk4=; b=oinvX9LsLJVlzDnUhzpmCViPlOSJ | |
s0VcGlalnd8LIJsaCCV529DQaTUYZbxuGNRNsxIpHu1AdfMjC4x2ZOgXCdoxMaLI | |
40DurDc6hWP0x+/QH0AK9VeNCEWPhLLXMrPk8S713WYJko7BRGcTbeM5CTChTHbY | |
YP0w9ywywFHnk3c= | |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Id: | <cygwin.cygwin.com> |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sourceware.org/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> |
Sender: | cygwin-owner AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
Delivered-To: | mailing list cygwin AT cygwin DOT com |
Authentication-Results: | sourceware.org; auth=none |
X-Virus-Found: | No |
X-Spam-SWARE-Status: | No, score=-4.6 required=5.0 tests=AWL,BAYES_50 autolearn=ham version=3.3.2 |
X-HELO: | calimero.vinschen.de |
Date: | Tue, 26 Aug 2014 15:12:30 +0200 |
From: | Corinna Vinschen <corinna-cygwin AT cygwin DOT com> |
To: | cygwin AT cygwin DOT com |
Subject: | Re: Update to latest cygwin creates crashes in dlclose() |
Message-ID: | <20140826131230.GC5740@calimero.vinschen.de> |
Reply-To: | cygwin AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
References: | <1408751151 DOT 18259 DOT YahooMailNeo AT web121005 DOT mail DOT ne1 DOT yahoo DOT com> <1408987842 DOT 26496 DOT YahooMailNeo AT web121002 DOT mail DOT ne1 DOT yahoo DOT com> |
MIME-Version: | 1.0 |
In-Reply-To: | <1408987842.26496.YahooMailNeo@web121002.mail.ne1.yahoo.com> |
User-Agent: | Mutt/1.5.23 (2014-03-12) |
--DIOMP1UsTsWJauNi Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Aug 25 10:30, Cary R. wrote: > >On Aug 22 16:45, Cary R. wrote: > >> I upgraded to the latest cygwin earlier today (it has probably been > >> a month or more since I last updated) and now a program that has been > >> working is crashing (segfault) when calling dlclose(). dlopen() and > >> calling a function in the DLL still works just fine. An older version > >> of the program still works correctly so it's not just simply calling > >> dlclose() but something more context dependent. >=20 > > Is you applications written in C++? >=20 > Yes the primary application is C++. The DLL is mixed C and C++. >=20 > > Does recompiling with the latest gcc 4.8.3-3 fix the issue? >=20 > make distclean, a reconfigure and then a complete recompile was the > first thing I tried when I noticed the failure and that did not fix > the crash. >=20 > > Typically a SEGV creates a stackdump file. Can you show us? >=20 > No stackdump file is being created. If I remove the call to dlclose() > the application does not SEGV and appears to run correctly. >=20 > Here is the output from gdb: >=20 > ~/src/verilog/iverilog-push/iverilog/vvp > gdb ./vvp-dev.exe > [...] > (gdb) run=C2=A0 -M../vpi ../../iverilog/vvp/examples/hello.vvp > Starting program: /cygdrive/c/src/verilog/iverilog-push/iverilog/vvp/vvp-= dev.exe -M../vpi ../../iverilog/vvp/examples/hello.vvp > [New Thread 4152.0x78c] > [New Thread 4152.0x1254] > Warning: vvp input file may not be correct version! > Hello, World. >=20 > Program received signal SIGSEGV, Segmentation fault. > 0x6314c658 in ?? () > (gdb) bt > #0=C2=A0 0x6314c658 in ?? () Hmm, YA case of __gcc_deregister_frame crashing? For a start you could check in which DLL this crash occurs. Call `rebase -si' and check in which DLL this address is on your system. I hazard the guess it's going to be /bin/cyggcc_s-1.dll... > > Last but not least, do you have a simple testcase to reproduce the issu= e? >=20 > I do not have a simple test case yet. Since this is an open source > application you could compile it to observe the behavior, but I was > planning to look into this more based on any feedback and my available > free time this week. Ok, I'll look into other stuff for now. Corinna --=20 Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat --DIOMP1UsTsWJauNi Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJT/Ie+AAoJEPU2Bp2uRE+gSg0P/Aubj5zm5OPjqPnqEARdQyQZ fIjXdJqI4bXCgv6Ki48fu1nGqoFNgJQK4YAxWBZ53N5MqQGsyWLmqfkVhSMXfZri LuqJuIS1BLOKH/HJVzBO3HVbvI0DGfTAfApIZixT3fZg+bGol4LQ/Ru77PIuZwu7 00ZGhA6+IhvVgoF8/6jXAiCf0TM67iPPYG78sTAc1CO2G6cRyYXeBkZoJ9LFzKHV VHrrDHgI0Trb6NK6B0fNOJxjem7uCuwjHWCC6VFn4nWJd+kPgpA5scYMMOqwJ6rW epHrd1zBzFeQafCGGVA4m8iyhadEIktAFBzQmHpNkdTdFoumJnrtRfJmElmGNk11 An3bTIfIT6BQJI83F5To3SkxxBJaG5wzNCol0KAhuXeM08Dektne5oyoe5uJ3D1T OQrSEErMtaKxZcFnnXuYPznarLR3lE8PiEgXU/VPfYWoujkBD9bs8Pjm7cZwOMX0 QyuDRmM1oDAGwedzaqyeCEqGKDIm7VW0Wyx3nkB9SqAEyA0DOBgYvIvNgf2rkRST uDIB5n9QNoB0lRo6J5NBe8DNJ1bBj3uSArTBgSy5HP0hBTzWJSGyHDE/aZsB2AUD b1JxYhSSCQLB8Qo/muQkh/TRwqB660XI7tm06TKEgob5tKrMOJV29kHyyT9gHLV8 sIr0e7MVU9c+oAidlW6K =e7SG -----END PGP SIGNATURE----- --DIOMP1UsTsWJauNi--
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |