Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
X-Authentication-Warning:	hp2.xraylith.wisc.edu: khan owned process doing -bs
Date:	Fri, 6 Jul 2001 12:19:39 -0500 (CDT)
From:	Mumit Khan <khan AT NanoTech DOT Wisc DOT EDU>
To:	Tom Tromey <tromey AT redhat DOT com>
cc:	Julian Hall <jules AT acris DOT co DOT uk>, cygwin AT cygwin DOT com, java AT gcc DOT gnu DOT org
Subject:	Re: Progress update with gcj on cygwin
In-Reply-To:	<87k81m9d72.fsf@creche.redhat.com>
Message-ID:	<Pine.HPP.3.96.1010706121627.25225D-100000@hp2.xraylith.wisc.edu>
MIME-Version:	1.0

On 6 Jul 2001, Tom Tromey wrote:

> >>>>> "Julian" == Julian Hall <jules AT acris DOT co DOT uk> writes:
> 
> Julian> I have now tracked the problem down to occurring during the
> Julian> stack unwinding process, which unfortunately I understand very
> Julian> little about.
> 
> I thought that the new unwind code was known not to work on Cygwin.
> Am I wrong?

You're correct. Dwarf2 based unwinding code does not work for any of
the x86 windows ports (Cygwin, Mingw, ...).

Until the proper changes are made to the startup code for Cygwin/Mingw/etc
in addition to some other changes in the x86 windows target specific code,
sjlj is it. 

Regards,
Mumit



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -