X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Date:	Wed, 11 Jun 2008 22:11:17 +0200
To:	cygwin AT cygwin DOT com
Subject:	g++ segfaults with new cygwin1.dll
From:	Maett <flaemflaem AT gmail DOT com>
MIME-Version:	1.0
Message-ID:	<op.uclo03fg7ejp8f@guido2>
User-Agent:	Opera Mail/9.27 (Win32)
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

Hi,

I have a cross-gcc 3.2.3 built at a time when Cygwin1.dll version 1.5.13
was current.
Now I want to update to a newer gcc version, so I built it with the current
Cygwin environment (with Cygwin1.dll version 1.5.25), and it runs ok.
But if I run my old gcc with the new Cygwin1.dll (1.5.25) it segfaults
for a c++ source which cimpiles ok with the old dll.
I can even rebuild gcc 3.2.3 on the current Cygwin, and it crashes on that
source.
What could be the reason that it segfaults with the new Cygwin1.dll but
not with the old one ?

(I have totally different pointer addresses; seems like the new Cygwin.dll
allocates memory at addresses from 0x7FFFFFFF down while the old one
allocated bottom up)

Maett


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

- Raw text -