Hi, I've noticed that the win32 version of fbclient (v2.5) is built using the synchronous exception model (i.e. using the /EHsc- option). This means that destructors for RAII objects such as the RefMutexGuard will not be called when a non C++ exception occurs (e.g. an Access Violation). When recovering from such an exception, a deadlock will occur. Is there any reason why fbclient should not be built using the asynchronous exception model (i.e. using the /EHa option)?
Thanks, Frank ------------------------------------------------------------------------------ Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
