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=Myr99K4Bh2nrAVPoX1iAe8Pg9j2hGUQE5gvqxGcbLp+NOP8PyhML6
	3nnE1jR2+bTogwKj8qM2/p0BwICsGH2WuennDGhtIjfYfvC5Z1P09zPXaIkgi5ob
	VTIJdTUi5Evi2Lo/Gk/d+/BLvxuA9xuwC1iYcFnLOBIOBWt/wW3tGo=
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=7Vhs7CogjXKIsTozU2d+fij66jI=; b=gB7uVStJS5/axLMwba4WpQMmfep1
	LmyFYpkfr027gOVSVkf9lFYGv3t57sn1a24CzykIXurEvKpDWvT/UyjUtxVwGfZw
	0I4v4NRm6ZePiAMGgsP3rgmaFQbISmLUrpf8h6jcSt64rnxmSfBFl/2ahZMQf2yI
	5vjvUwIK6nOdzlY=
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=-5.9 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2
X-HELO: calimero.vinschen.de
Date: Thu, 17 Jul 2014 20:24:29 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Core dump on 32-bit Cygwin if program calls dlopen
Message-ID: <20140717182429.GS15332@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <53C46ACD DOT 5060601 AT cornell DOT edu> <20140715090259 DOT GB20640 AT calimero DOT vinschen DOT de> <53C51460 DOT 5080805 AT cornell DOT edu> <20140715130829 DOT GK10401 AT calimero DOT vinschen DOT de> <53C532D9 DOT 7050506 AT gmail DOT com> <20140715143915 DOT GA8330 AT calimero DOT vinschen DOT de> <20140716070231 DOT GA25020 AT calimero DOT vinschen DOT de> <53C6F68A DOT 9000801 AT gmail DOT com> <20140717073734 DOT GA15332 AT calimero DOT vinschen DOT de> <53C7EC48 DOT 5060903 AT dronecode DOT org DOT uk>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="4eRLI4hEmsdu6Npr"
Content-Disposition: inline
In-Reply-To: <53C7EC48.5060903@dronecode.org.uk>
User-Agent: Mutt/1.5.23 (2014-03-12)

--4eRLI4hEmsdu6Npr
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Jul 17 16:31, Jon TURNEY wrote:
> On 17/07/2014 08:37, Corinna Vinschen wrote:
> >On Jul 17 06:02, JonY wrote:
> >>On 7/16/2014 15:02, Corinna Vinschen wrote:
> >>>On Jul 15 16:39, Corinna Vinschen wrote:
> >>>>On Jul 15 21:55, JonY wrote:
> >>>>>On 7/15/2014 21:08, Corinna Vinschen wrote:
> >>>>>>>
> >>>>>>>FWIW, the problem disappears if I revert gcc-core and libgcc1 to 4=
.8.2-2.
> >>>>>>
> >>>>>>JonY, do you have a chance to have a look into this issue?
> >>>>>
> >>>>>Sorry, I have been busy these few weeks, but I am well aware that th=
ere
> >>>>>is a problem with one of the libgcc changes, but has yet to investig=
ate it.
> >>>>>
> >>>>>I believe Jon Turney has looked into it somewhat.
>=20
> I think this is the same or a similar problem to the one I reported at [1=
].
> I also created a gcc bug [2], with a suggested patch.
>=20
> >>>>Sounds good.  Thanks in advance.
> >>>
> >>>Yesterday I asked my collegues to take a stab at the issue and one of
> >>>them, DJ Delorie, came up with a libgcc patch already.  It hasn't been
> >>>sent upstream yet.  Can we give it a try, perhaps by creating a new
> >>>libgcc DLL, please?
> >>
> >>Thanks, I'll get to it this weekend, should I make the new gcc an
> >>experimental version? Or is just the libgcc binary required?
> >
> >It's the libgcc DLL which gives us grief, so a new libgcc package is
> >sufficent, afaics.  We should check if this DLL fixes the problem and
> >then make it "curr" soon, I think.
>=20
> I briefly tested this other patch with my test case from the mail above, =
and
> it doesn't seem to help.
>=20
> On 15/07/2014 15:45, Jan Nijtmans wrote:
> > Is this essentially the same problem as described here?
> >
> >      <http://gcc.gnu.org/ml/gcc/2013-05/msg00180.html>
>=20
> No, I think it is an unforeseen consequence of the patch [3] to fix that =
bug
> [4], which I believe is present in 4.8.3-1, introducing a new problem when
> an executable which doesn't depend on libgcc dlopen()s a dll which does.
>=20
> [1] https://cygwin.com/ml/cygwin/2014-07/msg00083.html
> [2] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D61752
> [3] https://sourceware.org/ml/cygwin/2013-07/msg00528.html
> [4] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D57982

I asked DJ to take another look, but I guess ultimately we need the
attention of one of the GCC Windows maintainers.  Kai Tietz seems to be
unavailable right now, unfortunately.


Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--4eRLI4hEmsdu6Npr
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJTyBTcAAoJEPU2Bp2uRE+gYdgP/iwizCfwmxNFrLNGcLzL60n0
fIVvut2YZFVtXik1bpFJngtDXypdwn2rl9fkC/xVeciZzi/ZRcIsv/m/n7mVJ24A
60a45OpT1SVPbZXveTx3Awlv9RCXM/bjfiesaEB/UgPq8gfvKVTJ8mL3X6hWMF4v
J8qb0Go+db+DzmbHBizLy0bEQeOfF4Fy7Rhy35LaXq+gHu0RUTxG957VeEjj+ltM
snXqQkJTzmL1MnMZY8FkdcNW7IQycbF9unLOlN5IQPMsYA/nWD3SLrFssy+WZbJK
ZBWQCKmzD+vKpnTW1tAFIj8bP3I2gblSZJ1cWYBdKERVKE8EtKS5GxgZgs1Sx505
2j1mqQBiBkpgR0yE4MpEjzEaMKLNTmJX0qT6CXSJKSjnVOOaqqsViqtvzqNZLaPh
yhwYTPjcavYOQnrS+zSh+LmRtw6R83AQmR22UgkpbmzCjAU20fJMqZHniqDJWcTC
pvIdU+WoTPXwid7jLNVM4W0rmpXjWtd8IUxu/c9e6Zz6/73Ug8CAkniPAAq+/7wj
ovZOjOnWFg8Mq1JpD+PzA1isAY8c4lpm8aQuM2Zld8jn7WYtZMy9okn5WMURuOmi
uXIMwLbLxDwpUiXOp6GzwVFQE1y8aWxBsaiVRQMTOJNFfmLDqxf+Bqr2MZVVNC8m
dEE0jX4PO4puZhW4CGPb
=mX2Z
-----END PGP SIGNATURE-----

--4eRLI4hEmsdu6Npr--