Re: [gdal-dev] GDAL build on windows failed for FILEGDB driver

2024-03-01 Thread Even Rouault via gdal-dev
Le 01/03/2024 à 20:31, Fengting Chen via gdal-dev a écrit : Hi, I am using VS2015 terminal and cmake to build GDAL on windows. I got the following compilation error for filegdbindex_write.cpp. Any idea? I kind of remember there was a ticket about that (probably closed). Basically VS2015 ha

[gdal-dev] GDAL build on windows failed for FILEGDB driver

2024-03-01 Thread Fengting Chen via gdal-dev
Hi, I am using VS2015 terminal and cmake to build GDAL on windows. I got the following compilation error for filegdbindex_write.cpp. Any idea? E:\gdal-3.8.4\ogr\ogrsf_frmts\openfilegdb\filegdbindex_write.cpp(1388): note: while trying to match the argument list '(OpenFileGDB::FileGDBTable::Cr

Re: [gdal-dev] Alpine, gcc 32-bit in Linux Build Actions

2024-03-01 Thread Abel Pau via gdal-dev
Yes, I hope it's only ONE single mistake because I have my code very protected against that kind of things... Before you said that I am using LOG_STR(); from the test and I've filled it in all possible place it could be something. Remember I have windows and in Visual Studio it works fine... I

Re: [gdal-dev] Alpine, gcc 32-bit in Linux Build Actions

2024-03-01 Thread Even Rouault via gdal-dev
Your code must be something terrible so that even gdb doesn't catch it :-) (SIGKILL cannot be caught...) From the error messages, things might go wrong starting with https://github.com/OSGeo/gdal/blob/master/apps/test_ogrsf.cpp#L782 So maybe set a breakpoint at that line b test_ogrsf.cpp:782

Re: [gdal-dev] Alpine, gcc 32-bit in Linux Build Actions

2024-03-01 Thread Abel Pau via gdal-dev
It’s a mistery... INFO: MiraMonVector: Creation of /foo/test.pol should have failed. INFO: MiraMonVector: CreateFeature() at line 780 succeeded but failed to assign FID to feature. Program terminated with signal SIGKILL, Killed. The program no longer exists. (gdb) bt No stack. (gdb) I’ve compile

Re: [gdal-dev] Alpine, gcc 32-bit in Linux Build Actions

2024-03-01 Thread Even Rouault via gdal-dev
Under gdb, type "bt" (for backtrace) to see where it crashes. Normally Valgrind should display the stack trace too. It will be more reliable on a -DCMAKE_BUILD_TYPE=Debug build (assuming the issue is non Debug vs Release dependent) Le 01/03/2024 à 12:59, Abel Pau a écrit : Hi, and thanks for

Re: [gdal-dev] Alpine, gcc 32-bit in Linux Build Actions

2024-03-01 Thread Abel Pau via gdal-dev
Hi, and thanks for the answer. Valgrint give me that info ... INFO: TestCreate(JSONFG). INFO: JSONFG: Creation of /foo/test.json should have failed. INFO: JSONFG: CreateFeature() at line 780 succeeded but failed to assign FID to feature. INFO: TestCreate(MiraMonVector). INFO: MiraMonVector: Creat

Re: [gdal-dev] Alpine, gcc 32-bit in Linux Build Actions

2024-03-01 Thread Even Rouault via gdal-dev
Hi, this looks like potentially some memory usage issue that popups "randomly" on some platforms. The fact that you reproduce it on your 22.04 build is encouraging since it will make it easier to debug try the following: sudo apt-get install gdb valgrind gdb --args test_ogrsf -all_drivers ru

[gdal-dev] Alpine, gcc 32-bit in Linux Build Actions

2024-03-01 Thread Abel Pau via gdal-dev
Hi, yesterday I updated my personal branch (soon I'll do a pull request) but before as Even suggested I'm trying to make green al Actions. The only problem I have now is at some points on tests... But I am missing something because I there are things I don't understand well. Can anyone give me s