Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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 To: Tom Tromey cc: Julian Hall , 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: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On 6 Jul 2001, Tom Tromey wrote: > >>>>> "Julian" == Julian Hall 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/