Date: Thu, 10 Oct 2002 20:31:00 -0400 From: "Kevin B. Hendricks" <kevin.hendricks@sympatico.ca> To: dev@porting.openoffice.org, Martin Blapp <mb@imp.ch>, Alexander Kabaev <ak03@gte.com> Cc: <dev@porting.openoffice.org>, <openoffice@FreeBSD.ORG>, <kan@FreeBSD.ORG> Subject: Re: [porting-dev] FreeBSD: Uncatched exception problem Message-ID: <200210102031.00496.kevin.hendricks@sympatico.ca> In-Reply-To: <200210102010.56071.kevin.hendricks@sympatico.ca> References: <20021011004639.F15308-100000@levais.imp.ch> <200210102010.56071.kevin.hendricks@sympatico.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, One other thing, if it is over the component interface (possibly the bridge itself) then the shared libs would be dlopened and not directly linked. I am not sure if that is an importnat distinction but we could modify the test case to dlopen the libraries instead of linking directly to them. Again, this is just a wag. I would guess the best way to examine this issue to to create a debug version of the stack walkback code having it print out everyting it does during the walkback to see if something screams at us. Not being able to recreate it on my machine certainly makes debugging it a real guessing game. Sorry I can't be more help, Kevin On October 10, 2002 08:10, Kevin B. Hendricks wrote: > On October 10, 2002 07:59, Martin Blapp wrote: > Hi, > > Specifically have you tried changing optimization levels, adding > -fpermissive, -fexceptions, etc. > > Also, what about not using -fPIC (I use that becuase it is needed on ppc > Linux, but the x86 build doesn't always use it for some reason)? > > Perhaps compiling main with -fno-exceptions and using -fexceptions on > the two libs in the example? > > I am really grasping at straws here. Both methods in the real OOo code > are threaded so perhaps that matters? > > I will take another look at those routines to see ifanything strange > might be done (use of alloca etc) but I can't figure out why a throw > can't be caught by the catch just two frames up in the backtrace. It > makes no sense. > > Kevin > > > Hi Alexander, Kevin, > > > > > 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. > > > > Just did that. There is no change in the behaviour. Remember that > > I also used a version of linux's unxlngi4 includefile with the same > > settings to compile OpenOffice. No way. > > > > I also tried to compile everything with -frtti, but also no help. > > > > Martin > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@porting.openoffice.org > For additional commands, e-mail: dev-help@porting.openoffice.org 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?200210102031.00496.kevin.hendricks>