Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
To: cygwin AT cygwin DOT com
From: =?ISO-8859-1?Q?Ren=E9_Berber?= <rberber AT prodigy DOT net DOT mx>
Subject:  Re: 1.5.18: ld command generates stackdump
Date:  Sun, 09 Oct 2005 19:25:06 -0500
Lines: 28
Message-ID: <diccd2$s2d$1@sea.gmane.org>
References:  <045001c5cd2c$657579e0$1600a8c0 AT toyon DOT corp>
Mime-Version:  1.0
Content-Type:  text/plain; charset=ISO-8859-1
Content-Transfer-Encoding:  quoted-printable
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
In-Reply-To: <045001c5cd2c$657579e0$1600a8c0@toyon.corp>
OpenPGP: url=ldap://keyserver.pgp.com
X-IsSubscribed: yes

Peter J. Stieber wrote:

> I have a large simluation that I have built under cygwin for a quite a
> while. Recently the ld phase of the build started generating a stackdump
> (ld.exe.stackdump).
>=20
> Unfortunately I cannot recreate the problem with a simple test case. I
> have attached cygcheck output. I realize I'm not providing much
> information, but I am not sure what to do next.
>=20
> Would the stackdump be of use?

No, but the actual command line that caused the failure could be interestin=
g,
i.e. which libraries are being linked.

Any other error/waring messages before the failure?

> What should I do or provide to get some help?

Do you use any 3rd party packages?  I mean any libraries that don't come wi=
th
Cygwin.

Have you tried to do only the linking by hand?
--=20
Ren=E9 Berber


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/