I use 
try{
    function_call();
}catch(...)
{
    handler();
}

but still got BOINC's debugger called... 

----- Original Message ----- 
From: "Rom Walton" <r...@romwnet.org>
To: "Raistmer" <raist...@mail.ru>; <boinc_dev@ssl.berkeley.edu>
Sent: Friday, October 16, 2009 8:59 PM
Subject: RE: [boinc_dev] Disabling BOINC's debugger


The exception handling code on Windows only kicks in if no other
exception handling mechanism is used.

Just define an exception handler of some sort and you should be good to
go.

Just remember, on Windows there are two different exceptions that can be
thrown.  C++ exceptions and SEH exceptions.  C++ exceptions use the
try()/catch() stuff everybody is used too, SEH exceptions use
__try/__catch.

----- Rom 

-----Original Message-----
From: boinc_dev-boun...@ssl.berkeley.edu
[mailto:boinc_dev-boun...@ssl.berkeley.edu] On Behalf Of Raistmer
Sent: Friday, October 16, 2009 12:50 PM
To: boinc_dev@ssl.berkeley.edu
Subject: [boinc_dev] Disabling BOINC's debugger

Hello
Is it possible to give control for exception handling back to science
app?
What BOINC API call I should comment out to do this?
Need exception handling inside app....to catch exception instead of
writing 
to stderr and trashing task...

_______________________________________________
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

_______________________________________________
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Reply via email to