Open PISERERER opened 3 months ago
as I not only compiled GDAL on my machine but also added the
PGeo
driver to the official ARM version of theGDAL Docker image
which docker image exactly? We have 4 variants. So this does work on Arm with a GDAL Docker image, but not in your native environment? Personally, I won't be able to investigate now owing a Mac
as I not only compiled GDAL on my machine but also added the
PGeo
driver to the official ARM version of theGDAL Docker image
which docker image exactly? We have 4 variants. So this does work on Arm with a GDAL Docker image, but not in your native environment? Personally, I won't be able to investigate now owing a Mac
Yes, it runs normally in the ARM-based Docker image container, which is also running on Docker on my Mac, but there are issues in my local MacOS ARM environment. I am using this image: https://github.com/OSGeo/gdal/pkgs/container/gdal/180417381?tag=ubuntu-full-3.8.4 I noticed one difference: in the image, the unixODBC version is 2.3.9.
What is the bug?
I compiled GDAL 3.8.5 with support for the
PGeo
driver on anM1 MacOS
, but when I ran the commandogrinfo --debug on -if PGeo 640122HLX_2006Y00_SV050_P.mdb
, I received the following debug information:Additionally, the program becomes unresponsive and cannot be stopped, while consuming 100% CPU on a single core (possibly due to an infinite loop?). One particularly valuable piece of information was:
'PGEO: SELECT on GDB_GeomColumns fails, perhaps not a personal geodatabase?'
I attempted to trace the GDAL source code and by adding debug information, it seems that the issue occurs when executing the following SQL statement:Continuing the trace, it appears that the
SQLExecDirect
method returns-2
, but no valuable error information is captured. As I am not very familiar with C++, I am unable to further trace the issue. It is clear, however, that theSQLExecDirect
method is fromunixODBC
(if I understand correctly).Furthermore, I tried executing the problematic SQL statement directly through
unixODBC
and encountered no issues. I configured the mdb file inodbc.ini
and used theisql
command to read it as follows:I am confident that there is no issue with the mdb file itself, as I not only compiled GDAL on my machine but also added the
PGeo
driver to the official ARM version of theGDAL Docker image
. I then executed the same command against the same mdb file within the container and obtained the correct results. The output was as follows:Steps to reproduce the issue
Install unixODBC, mdbtools, etc., compile GDAL 3.8.5, and execute the command: ogrinfo --debug on -if PGeo xxx.mdb. The compilation command is as follows:
Versions and provenance
M1 pro MacOS 14.4.1
Additional context
No response