Re: [DebianGIS] qgis-plugin-grass problem on sid
On 11/10/05, Didrik Pinte <dpinte@itae.be> wrote:
> Ps : the full log is here : http://itae.be/downloads/qgis.log
Didrik,
The important error message (the first related one) is:
==11964== Invalid write of size 4
==11964== at 0x1C2A5C74: GDALDriver::GDALDriver() (in
/usr/lib/libgdal.so.1.9.0)
==11964== by 0x1F0F6699: GDALRegister_GRASS (in
/usr/lib/gdalplugins/gdal_GRASS.so)
==11964== by 0x1C2A758C: GDALDriverManager::AutoLoadDrivers() (in
/usr/lib/libgdal.so.1.9.0)
==11964== by 0x1C1F807E: GDALAllRegister (in /usr/lib/libgdal.so.1.9.0)
==11964== by 0x817C680:
QgsRasterLayer::buildSupportedRasterFileFilter(QString&) (in
/usr/bin/qgis)
==11964== by 0x80CEF2D: QgisApp::QgisApp(QWidget*, char const*,
unsigned) (in /usr/bin/qgis)
==11964== by 0x80B5713: main (in /usr/bin/qgis)
==11964== Address 0x1E169E44 is 0 bytes after a block of size 36 alloc'd
==11964== at 0x1B8FFC22: operator new(unsigned) (vg_replace_malloc.c:164)
==11964== by 0x1F0F6688: GDALRegister_GRASS (in
/usr/lib/gdalplugins/gdal_GRASS.so)
==11964== by 0x1C2A758C: GDALDriverManager::AutoLoadDrivers() (in
/usr/lib/libgdal.so.1.9.0)
==11964== by 0x1C1F807E: GDALAllRegister (in /usr/lib/libgdal.so.1.9.0)
==11964== by 0x817C680:
QgsRasterLayer::buildSupportedRasterFileFilter(QString&) (in
/usr/bin/qgis)
==11964== by 0x80CEF2D: QgisApp::QgisApp(QWidget*, char const*,
unsigned) (in /usr/bin/qgis)
==11964== by 0x80B5713: main (in /usr/bin/qgis)
==11964==
This essentially indicates that the GDALDriver() constructor code
tried to initialize a field off the end of the memory block allocated
by new for the driver in GDALRegister_GRASS(). The size of the
GDALDriver specific stuff hasn't changed in some time, but I recently
changed the size of the GDALMajorObject base class. I would be willing
to bet the problem you are encountering is due to the grass plugin
having been compiled against a different version of GDAL than
you are using.
It is extremely dangerous for GDAL and OGR plugins to be used
if they were built against a different version of GDAL than the one
they will be loaded by.
I think we need to trace back to the GDAL and GDAL GRASS driver
binary packages you are using and verify they are compatible. I
am not sufficiently familiar with .deb mechanics to do that though.
Best regards,
--
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up | Frank Warmerdam, warmerdam@pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush | Geospatial Programmer for Rent
Reply to: