[gdal-dev] Building with SEH

[mchapman at texelinc.com]

Chris,

I would handle an error like this by stepping through the gdal source code file with your debugger and try to see what line and what file it is crashing on.  Is the gdal .pdb file in the same directory as your application exe? Are you able to step into the gdal source with your debugger on the call that crashes gdal (f11)? There is most likely a null pointer being used somewhere is my guess.  If you can't solve it send me the bad shape file and I will look at it.

Best regards,
Martin

Sent via BlackBerry by AT&T

-----Original Message-----
From: "Chris Howell" <chowell at pyxisinnovation.com>

Date: Tue, 11 Mar 2008 22:25:20 
To:<gdal-dev at lists.osgeo.org>
Subject: [gdal-dev] Building with SEH


Hi All,
 
 Currently there is an error with one of the drivers in OGR whereby if a corrupted or just generally malformatted shape file is attempted to be opened through OGR, there is an exception that is generated in the VC Runtime, where OGR completely crashes and I can't trap the exception to handle it at application level because the runtime is crashing. What I am wondering about is there a way I can compile GDAL with SEH enbabled turning exceptions that are generated at the OS level into standard C++ exceptions I can trap and handle appropriately ? I looked in the make file and the options file and didn't seen anything obvious.
 
 Any light anyone can shed on this would be greatly appreciated.
 
 Cheers
 Chris Howell
 Software Engineer
 the PYXIS innovation
 www.pyxisinnovation.com
 _______________________________________________
gdal-dev mailing list
gdal-dev at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev