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
Message-ID:	<20050103022643.81396.qmail@web30903.mail.mud.yahoo.com>
Date:	Sun, 2 Jan 2005 18:26:43 -0800 (PST)
From:	Bill Priest <priestwilliaml AT yahoo DOT com>
Subject:	STLport on cygwin exception problem
To:	cygwin AT cygwin DOT com
MIME-Version:	1.0

All,
  In porting STLport (STLport_r50 from cvs) I've run
into a problem where a couple of the unit tests
involving
exception handling for out of range errors aren't
caught.  I've reduced one test case down to be
fairly minimal.  I've run the same version w/ the same
version of gcc on Linux and these same tests work.
I downloaded the 20050101-1 snapshot and it misbehaves
in a similar fashion.  I next tried Danny Smith's
dwarf2 patch to gcc to see if it was a sjlj problem;
still no improvement.  I've debugged it using gdb and
it seems that in unwinding the stack that the catch
of the exception fails (I'm not a c++ expert by any
means); so my diagnosis could be off.
  The allocation of the exception is successful; the
problem appears to be in Unwind_RaiseException.  No
handler is found before end of stack is detected.
The fs data structure in unwind.inc is a mystery to
me.  I'll keep digging; some how the catch has to
"register" some information in the context at the
higher level and then in the lower level when the
exception is thrown the unwind should find the
exception?

Any pointers or hints in debugging this problem would
be appreciated.

Bill



		
__________________________________ 
Do you Yahoo!? 
Send a seasonal email greeting and help others. Do good. 
http://celebrity.mail.yahoo.com

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