[gdal-dev] [External] : Re: GDAL driver Open() calls

[Fengting Chen]

Hi Even,

Here is what found out from debugging: There are two Open() calls. Your fix skipped one. Here is the stack trace of the second one:

[cid:image001.png at 01DA239D.5F51E090]

Thanks!

From: Even Rouault <even.rouault at spatialys.com>
Date: Thursday, November 30, 2023 at 8:40 AM

Le 30/11/2023 à 04:47, Fengting Chen a écrit :
This doesn’t seem to fix the problem. How do I print out the stack trace in the driver?

This is not something the driver can do. You have to use the interactive debugger of your dev environment, attach it to your gdal_translate command, set a breakpoint in the GeoRasterDataset::Open method, and use the appropriate function of your debugger to display the call stack. I'm sure you'll find plenty of online resources for whatever debugger you use.

Even



--

http://www.spatialys.com<https://urldefense.com/v3/__http:/www.spatialys.com__;!!ACWV5N9M2RV99hQ!LdunXkjoOPFddx-jqp6_eWkk746TTCmRdAPcBj35cB2LBYcxMogtL6zHZEup8CJ2DN0T62IvlW7uYshKVkU9PsDwZbPE$>

My software is free, but my time generally not.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20231130/f3ea8246/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 32147 bytes
Desc: image001.png
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20231130/f3ea8246/attachment-0001.png>