Date: Thu, 10 Oct 2002 20:45:25 -0400 From: "Kevin B. Hendricks" <kevin.hendricks@sympatico.ca> To: Alexander Kabaev <ak03@gte.com>, Martin Blapp <mb@imp.ch> Cc: dev@porting.openoffice.org, openoffice@freebsd.org, kan@freebsd.org Subject: Re: [porting-dev] FreeBSD: Uncatched exception problem Message-ID: <200210102045.25098.kevin.hendricks@sympatico.ca> In-Reply-To: <20021010182724.14cdb1b3.ak03@gte.com> References: <200210101456.42050.kevin.hendricks@sympatico.ca> <20021011002442.J15308-100000@levais.imp.ch> <20021010182724.14cdb1b3.ak03@gte.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi,
One thing the bridge code does a lot of is to use alloca for space in the
current frame. This at one time in gcc 2.95.3 created problems for stack
walkbacks on ppc linux.
Perhaps we should change the test code to make sure the routine that does
the catch uses alloca a number of times (and memset that space to 0) to
make sure that growing the stack frame dynamically does not cause problems
for the walkback.
So somewhere before the "try" in test2lib.cxx you might want to add the
following lines:
#include <alloca.h> // or whatever the right header is
void* pSpace = NULL;
int n = 20;
for( int i = 0; i < n; i++ )
{
pSpace = alloca( n*(i+1) );
memset( pSpace, 0, n*(i+1) );
}
To force that frame to grow to see if that has any impact on the walkback.
Kevin
On October 10, 2002 06:27, Alexander Kabaev wrote:
> On Fri, 11 Oct 2002 00:25:06 +0200 (CEST)
>
> Martin Blapp <mb@imp.ch> wrote:
> > Hi Kevin,
> >
> > > in do_it throwing 15
> > > caught struct Exc&
> >
> > I get the same result :/
> >
> > Martin
>
> You should compile and link this sample using the same options OO uses
> to compile its components. The simple case of exceptions being thrown
> across shared libraries is working fine, I assure you.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-openoffice" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200210102045.25098.kevin.hendricks>