[omniORB] Why isn't the exception thrown taken care of by thecatch(...)

[David Konerding]

"ERIKSSON,TOBIAS (A-Sweden,ex1)" wrote:

> In other words, it is a compiler error. But will it help if I like you
> David, recompile g++ with whatever is the latest source for g++, are there
> some tuning that needs to be done. And the problems you had with STL, have
> you been able to see what that was, are the problems still there?
>
> Strange thing is that I browsed GNU's home page the other day for GCC/G++
> and couldn't really find anything about problems with exceptions, but on the
> other hand I just browsed through the updates beeing done. Furthermore I
> seem to have pretty much the latest version i.e. 2.95.2 20000220 (Debian
> GNU/Linux)
>
> /Tobias
>

Nope, recompiling g++ 2.95.2 with g++ 2.96(redhat) will not help.  It's actually
in the source code
If you want to learn more about this issue, go to the gcc mailing list archives.

Oh, I seeyou are using Debian instead of Red Hat.  Well, I wonder-- did you
compile omniORB your self or get a binary from somewhere else?  I usually
compile everything -- *everything* from scratch with a
single compiler, and with -g and without -fomit-frame-pointer, and that seems to
fix it.

As for the STL problem, no I did not solve it, but it appears to be a 2.96
issue.  We'll see- for the time being, I'm sticking to Red Hat 6.2 and gcc
2.95.2, since that works for us.