On Tue, 25 Jun 2024, Even Rouault via gdal-dev wrote:
ok, so the exception occurs in the embedded copy of tinyxml inside the ECW
SDK ?
You likely need to apply those community patches to your libecwjp2 3.3
sources:
https://github.com/rouault/libecwj2-3.3-builds/blob/main/libecwj2-3.3.patch
ok, so the exception occurs in the embedded copy of tinyxml inside the
ECW SDK ?
You likely need to apply those community patches to your libecwjp2 3.3
sources:
https://github.com/rouault/libecwj2-3.3-builds/blob/main/libecwj2-3.3.patch
Le 25/06/2024 à 18:42, Andrew C Aitchison a écrit :
On
On Tue, 25 Jun 2024, Even Rouault via gdal-dev wrote:
Le 25/06/2024 à 16:52, Andrew C Aitchison a écrit :
On Tue, 25 Jun 2024, Even Rouault wrote:
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/testclo
Le 25/06/2024 à 16:52, Andrew C Aitchison a écrit :
On Tue, 25 Jun 2024, Even Rouault wrote:
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
On Tue, 25 Jun 2024, Even Rouault wrote:
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
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
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:
(gdb) run
Starting program:
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")
Le 25/06/2024 à 15:14, Andrew C Aitchison via gdal-dev a écrit :
This is not a new failure, so thre
This is not a new failure, so thre is no need for this to hold up 3.9.1.
System: Ubuntu 24-04/Noble on Intel x86-64.
# ctest --output-on-failure
8< 8< 8< 8< 8< 8< 8<
28/51 Test #28: test-closed-on-destroy-DM ***Failed0.19 sec
[==] R
