Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@sources.redhat.com>
List-Help: <mailto:cygwin-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@sources.redhat.com
Delivered-To: mailing list cygwin@sources.redhat.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@NanoTech.Wisc.EDU>
To: Tom Tromey <tromey@redhat.com>
cc: Julian Hall <jules@acris.co.uk>, cygwin@cygwin.com, java@gcc.gnu.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
Content-Type: TEXT/PLAIN; charset=US-ASCII

On 6 Jul 2001, Tom Tromey wrote:

> >>>>> "Julian" == Julian Hall <jules@acris.co.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/