[osgeo4w-dev] proj refactoring, gdal17-ecw

[Benoit de Cabissole]

 Hi Frank,

No such luck for me either! I'm on winXP SP3 using QGIS (1.6 R14423)
OSGeo4W with the GDAL plugin (raster) and gdal1.7-ecw installed.
Well, every time a GDAL program is run through the plugin (I've used
GDALinfo & WRAP) its bombs out right.

In the QGIS GDALinfo plugin window no results are displayed, but on a
DOS console the info is displayed and then GDALinfo bombs out. Same
behaviour for WRAP, it bombs out right at the end, after the output file
is correctly created on disk.

Your diagnostic seems to be the correct one.

HTH,
Benoit

 

On 25/10/2010 15:57, Frank Warmerdam wrote:
> Matt Wilkie wrote:
>> Many thanks for this work Frank!
>>
>>  > http://trac.osgeo.org/osgeo4w/wiki/pkg-gdal17-ecw
>>
>> After following these instructions gdalinfo works, in that it reports
>> info I expect, but throws up a crash dialog (attached). I'm using
>> 64bit Win7 and put the ecw dll's in %osgeo4w_root%\bin.
>>
>
> Matt,
>
> Hmm.  Unfortunately it crashing at the point the dataset is destroy is
> consistent with the behavior I would expect in a "cross runtime heap
> corruption" problem which seems likely in this situation.  I'm going to
> test on a few more systems here.  But I suspect it just isn't safe to
> build GDAL plugins with VC9 when GDAL itself is built with VC7.1.
>
> Based on my success with the gdal-dev package, it might be reasonable for
> me to also try and upgrade the gdal-17 package to use VC9 and then I
> could
> have a consistent compiler for GDAL and the plugin.  Alternatively I
> could remove the gdal17-ecw plugin and deploy one with gdal 1.8 when
> it is
> released and packaged.
>
> For now, I'll wait to see how many others run into similar problems. 
> It may
> be that Windows 7 is more sensitive to heap corruption at the end of
> process
> life than XP.
>
> Best regards,