[Gdal-dev] ECW Problems?

[Bill Binko]

Hi everyone

I've been using Mapserver mainly for vector data, and now have some 
rasters (DOQQs) that I'd like to integrate.  Unfortunately, they came as 
ECW files and I'm using a Linux box, so I think I have some work cut out 
for me.

I have built GDAL CVS HEAD using the binaries for ERMapper's libs from 
gdal.org (they're the only ones that I could get to download).

The problem is that I'm getting a thread that hangs around at the end of 
any of the gdal* commands.  For example, here's what I get when I run the 
gdalinfo on one of the files:

#0  0xffffe410 in ?? ()
#1  0xbfff5968 in ?? ()
#2  0x409ba164 in ?? () from /usr/lib/libNCSUtil.so
#3  0x00000000 in ?? ()
#4  0x404b2ba6 in __nanosleep_nocancel () from /lib/tls/libpthread.so.0
#5  0x409b6408 in NCSSleep () from /usr/lib/libNCSUtil.so
#6  0x409b17ba in CNCSThread::Stop () from /usr/lib/libNCSUtil.so
#7  0x4052e164 in CNCSJP2FileView::Shutdown () from /usr/lib/libNCSEcw.so
#8  0x40526ad9 in CNCSJP2FileView::~CNCSJP2FileView () from /usr/lib/libNCSEcw.so
#9  0x404fd6d4 in CNCSFile::~CNCSFile () from /usr/lib/libNCSEcw.so
#10 0x400ced35 in ECWDataset::~ECWDataset () from /usr/lib/libgdal.so.1
#11 0x401780b7 in GDALClose () from /usr/lib/libgdal.so.1
#12 0x0804a41f in main ()

It looks like a fun pthread concurrency problem.  I'll be happy to attack 
it, but I really don't want to go through this if it's not necessary.

Has anyone been looking at this?  I saw a note a few months ago that might 
be this, but nothing since.

Thanks
Bill

PS: where can I get the ERMapper SDK source?