Re: [ROOT] CINT: exceptions on Linux?

From: Christoph Bugel (chris@tti-telecom.com)
Date: Fri Aug 10 2001 - 17:20:42 MEST


I also heard (rumors about) such bugs, but AFAIK these were, indeed, old
versions of gcc. I am using gcc 3.0, and I am *quite* sure this has been fixed.
At least I can throw and catch exceptions with gcc 3.0 / Linux between shared
objects, without any problem. I suspect I made a mistake with my Cint
compilation settings.
(And you are right about the 'abort' message :)

Thanks,
Christoph

On Fri 2001-08-10, mathes@ik3.fzk.de wrote:
> Hi Christoph,
> 
> just one idea concerning your problem ...
> In the Manula of the MICO Orb I read that there are some compilers (mainly
> gcc 2.7, gcc 2.8 and egcs) which cannot catch exceptions from shared
> libs. So which compiler do you use and did you throw the exception from
> code compiled into a shared lib ?
> In this case event catch (..) doesn't help.
> 
> The 'abort' is from my experience the normal reaction on an uncatched
> exception ...
> 
> Hermann-Josef
> 
> 
> On Thu, 9 Aug 2001, Christoph Bugel wrote:
> 
> > Hi,
> > 
> > I am having some problems throwing exceptions from my compiled objects and
> > catching them, outside cint, in my compiled main(). (Abort, core dumped).
> > Before I start digging into this I just wanted to ask if there are any known
> > issues with this on Linux? I think I simply did something wrong myself, but
> > asking never hurts.  (and I don't have this problem on solaris and on windows.)
> > 
> > BTW, On windows, G__STD_EXCEPTION is defined, by default, by the following code
> > in G__ci.h, so I had to uncomment the #define line, otherwise I could not catch
> > exceptions by myself, cint would catch them before I could.
> > 
> > #if defined(G__WIN32) && !defined(G__STD_EXCEPTION)
> > #define G__STD_EXCEPTION  // I commented this line out!
> > 
> > Thanks,
> > Christoph
> > 
> 



This archive was generated by hypermail 2b29 : Tue Jan 01 2002 - 17:50:57 MET