[Gdal-dev] ECW File open failed

[Ken Sewell]

Ok, I've traced through gdalinfo.  For anyone who's interested I found 
that gdb seems to get stuck in libecwj2-3.3/Source/C/NCSUtil/mutex.c in 
the function NCSMutexEnd:265 with the call to

pthread_mutex_unlock(&(pMutex->m));

After that point I get a 

Cannot access memory at 0x7fffffff4fb0

and gdb won't go on.  I'm not very knowledgable with pthreads, so I'm not 
sure what else I can do at this point.  Since it seems like a libecw 
issue at this point so I'm going to list it on the ecwsdk 3.3RC1 feedback 
page.  Unless any pthread guru's have any advice, I guess GDAL/ECW will 
have to go onto the back burner until ecwsdk 3.3rc2.

Ken

On Tue, 7 Feb 2006, Frank Warmerdam wrote:

> On 2/7/06, Ken Sewell <sewell at dramail.com> wrote:
> >
> > Yes, "gdalinfo --formats" does list "ECW (rw)"
> >
> > I went ahead and downloaded the 3.3 RC1 and tried it on my 32-bit and my
> > 64-bit.  gdalinfo on both machines show ECW in the formats list.  ECW on
> > the 32-bit seems to work, same error on the 64-bit.  The examples
> > included with ecwsdk3.3rc1 do run on the 64-bit system.  I'm trying to
> > dig further.  Is there an easy way to build a debug version of gdal?  I
> > haven't found a config option or a makefile target to do this yet.
> 
> Ken,
> 
> How to build GDAL in debug mode is a closely guarded secret.
> But if you promise not to tell anyone else, I'll pass it on.
> 
> Set the CFG environment variable to debug before building and
> the debug options will be used.
> 
> eg.
> $ export CFG=debug
> $ make
> 
> Remember, it's secret.  I do this in a completely nonstandard
> way to ensure no one but me (and now you) can debug GDAL.
> 
> Best regards,
> --
> ---------------------------------------+--------------------------------------
> 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 Programmer for Rent
>