On 11/30/06, Salikh Zakirov <[EMAIL PROTECTED]> wrote:
Evgueni Brevnov wrote:
> Let's leave the -D or -X dilemma for a while. Nina Rinskya and me
> found more serious problem. The problem is that debug windows popups
> even if -Dvm.assert_dialog=false is specified. It happens because each
> dll has its own copy of the variable which controls the behaviour of
> an assert macro. In other words when you change the report mode by
> calling _CrtSetReportMode it affect the current dll only. So if
> assertion fails in any other dll we will see debug window.
>
> Any ideas how to fix that?
A question, just to verify understanding:
does portlib-style signal catching, which is done in launcher,
misses these application errors too?
Yes it does. When assert fails it creates debug window explicitly. So
there is no connection between exception handlers and assert
statements.
I was under impression that stock version of launcher does not allow
any uncaught exception to slip through.
No exception is generated if assert fails....
