[gdal-dev] GDAL 1.10 JP2000 Problem/Crash

Frank Warmerdam warmerdam at pobox.com
Thu May 23 10:37:33 PDT 2013

On Thu, May 23, 2013 at 9:07 AM, John Daniel <jdaniel at usgs.gov> wrote:

> Even,
> Is this crash specific to GDAL 1.10? We have been using the old ECW
> library for a couple of years with good success. It is a bit buggy. I never
> did get it running on Solaris. We are still on GDAL 1.9.2.


In my experience the crashes with the ECW 3.3 library are not specific to
recent versions of GDAL.  I've run into them over the years.

> I have been worried about this old ECW library blocking us from future
> updates. We are testing Kakadu right now. If ECW has problems in GDAL 1.10,
> that would be important to know.
> Are there any issues with Kakadu and GDAL 1.10? I'm worried about the way
> GDAL links directly to Kakadu object files instead of using the library.

I am not aware of any problems with Kakadu and GDAL 1.10.  If you run into
something i'd be interested in fixing it.

Why does the direct use of the app directory object files concern you?  I
can't recall exactly why it is setup that way.  It seems to me I once tried
to use the library for the apps area but it was missing something I needed.
 It seems the current arrangement is just a bit ackward but hopefully not a
serious barrier for Kakadu licensees.

Best regards,

 even.rouault at mines-paris.org <even.rouault at mines-paris.org>> wrote:

> > Le mercredi 22 mai 2013 19:22:09, Frank Warmerdam a écrit :
> >> Dennis,
> >>
> >> Ah.  In my experience the ECW SDK 3.3 JPEG2000 support is buggy and I
> was
> >> never really able to trace down the issues.  I would encourage you to
> >> consider alternatives - one possibility is the MrSID SDK's JPEG2000
> >> support.  If Tamas's build includes MrSID support then all you need to
> do
> >> is set the GDAL_SKIP environment variable to JP2ECW which would make
> >> skip the ECW based driver.   If Tamas hasn't built with MrSID then it
> falls
> >> to you to build GDAL which can be somewhat complicated.
> >
> > I can replicate the crash with the JP2ECW driver with ECW SDK 3.3. It
> occurs
> > actually in the SDK itself, not in GDAL, so nothing that we can really do
> > about that (except using GDAL API Proxy, see below). Newer versions of
> the SDK
> > don't produce this crash.
> _______________________________________________
> gdal-dev mailing list
> gdal-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/gdal-dev

I set the clouds in motion - turn up   | Frank Warmerdam,
warmerdam at pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush    | Geospatial Software Developer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20130523/07c6292a/attachment.html>

More information about the gdal-dev mailing list