RE: [Firebird-devel] error handling appears to be broken

[Samofatov, N. <Nickolay@BroadViewSoftware.com>]

Hi, Alex!

> It seems to me that (at least in fun.epp for MSVC6 build)=20
> erro handling is broken.

It is not broken, it is fixed. :)

Structured exception handler passes error to outer handler for
debugging, etc instead of silently doing exit().

> SEH doesn't work at all with current compiler settings. If I=20
> emulate, for example, access violation (c0000005) in UDF, it=20
> remains unhandled and I see standard windows dialog - OK to=20
> cancel, Cancel to debug. On the other hand, C++ try/catch=20
> catches AV successfully, and I can process it in catch(...)=20
> block. Though I must notice that given UDF was compiled using=20
> that same MSVC, and therefore this test can't be treated as final.
> Before continuing with this problem, I'd like to know other=20
> peoples mind
> - why besides historical reasons do we use __try/__except=20
> error handling in win32? What benefits  does it have via C++=20
> try/catch?

There is no good way of accessing exception context from C++ exception
handler. For structured exception you can see the exception type and
various parameters.

> Alex.

Nickolay