Posted by
Luigi Ballabio on
Jul 13, 2010; 12:58pm
URL: http://quantlib.414.s1.nabble.com/catching-access-violation-compiler-settings-and-xl-addin-crash-tp12120p12121.html
On Fri, 2010-06-11 at 09:49 +0800, P Nelnik wrote:
> Due to the current quantlib compiler settings, access violations are
> not caught with catch(...)
> as a result we can have some rather ungraceful crashes.
>
> I wonder are there reasons why the settings are the way they are?
I don't think there's a particular reason. It might have been ported
from an earlier compiler version, or the compiler defaults. We just
didn't give it much thought.
> I'd suggest changing the settings.
> To do this in MS Visual C++ 2008, click on:
> Project -> Properties -> Configuration Properties -> C/C++ -> Code
> Generatoin
> and set:
> Enable C++ Exceptions
> to
> Yes With SEH Exceptions (/EHa)
> rather than
> Yes ( /EHsc)
Ok, I'll do it for next release. Does the setting just add some
error-catching code, or is there any binary-compatibility issue to be
aware of?
Luigi
--
Steinbach's Guideline for Systems Programming:
Never test for an error condition you don't know how to handle.
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first --
http://p.sf.net/sfu/sprint-com-first_______________________________________________
QuantLib-dev mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/quantlib-dev