Re: [QGIS-Developer] Calling for assistance - Windows MVSC builds not catching GEOS exceptions?

On 2 March 2018 at 20:38, Jürgen E. Fischer wrote: > Hi Hugo, > > On Fri, 02. Mar 2018 at 10:48:21 +0100, Hugo Mercier wrote: >> I know there are some issues when an exception is thrown from a DLL compiled >> with a different runtime version (i.e. different compiler version) than

Re: [QGIS-Developer] Calling for assistance - Windows MVSC builds not catching GEOS exceptions?

Hi Hugo, On Fri, 02. Mar 2018 at 10:48:21 +0100, Hugo Mercier wrote: > I know there are some issues when an exception is thrown from a DLL compiled > with a different runtime version (i.e. different compiler version) than the > DLL/EXE trying to catch it. >

Re: [QGIS-Developer] Calling for assistance - Windows MVSC builds not catching GEOS exceptions?

Hi Nyall, I know there are some issues when an exception is thrown from a DLL compiled with a different runtime version (i.e. different compiler version) than the DLL/EXE trying to catch it. https://stackoverflow.com/questions/5107948/throwing-c-exceptions-across-dll-boundaries Could it be the

[QGIS-Developer] Calling for assistance - Windows MVSC builds not catching GEOS exceptions?

Hi all, While investigating Anita's "most annoying issue", https://issues.qgis.org/issues/14752 I've tracked this down to certain calls to geos functions crashing on Windows builds alone. The situation is that the geos exception handler, throwGEOSException is correctly called, which triggers a