[gdal-dev] testclosedondestroydm.test

[Even Rouault]

Le 25/06/2024 à 16:25, Andrew C Aitchison a écrit :
> On Tue, 25 Jun 2024, Even Rouault via gdal-dev wrote:
>
>> Can you run "gdb autotest/cpp/testclosedondestroydm" , "run" , and 
>> when it crashed "bt" so we have a backtrace of where it crashes  (all 
>> of that after running "source ../scripts/setdevenv.sh")
>
> It doesn't crash:

Ah, the gtest framework must catch the exception. OK, so after starting 
gdb and before "run", type "catch throw", so that debugger stops when 
the exception is thrown, and then "bt"


>
> I do not have the MrSID SDK, so not recognizing mercator.sid is expected.

yes, a number of error messages in that test are expected depending on 
which drivers are there / not there, and will not make it fail. The 
FAILED you get is related to a unexpected C++ exception


-- 
http://www.spatialys.com
My software is free, but my time generally not.