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

2024-03-04 Thread Abel Pau via gdal-dev 
Well,
I've also found that issue: strdup (s=0x0)   Found and corrected.
It's was also a big issue :$

#0  __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74
#1  0x74fa8583 in __GI___strdup (s=0x0) at ./string/strdup.c:41
#2  0x76f4c075 in MMInitLayerToRead (hMiraMonLayer=0x560b57e0, 
m_fp=0x55d5e590,
pszFilename=0x55d4f970 "/vsimem/test1067.pol") at 
/gdal/ogr/ogrsf_frmts/miramon/mm_rdlayr.c:146
#3  0x76f2e03a in OGRMiraMonLayer::OGRMiraMonLayer (this=0x56087b10,
pszFilename=0x55d4f970 "/vsimem/test1067.pol", fp=0x0, poSRS=0x0, 
bUpdateIn=0, papszOpenOptions=0x0,
MMMap=0x5607b5c0) at 
/gdal/ogr/ogrsf_frmts/miramon/ogrmiramonlayer.cpp:219
#4  0x76f2c8b5 in OGRMiraMonDataSource::Open (this=0x5607b460,
pszFilename=0x55d4f970 "/vsimem/test1067.pol", fp=0x0, poSRS=0x0, 
bUpdateIn=0, papszOpenOptionsUsr=0x0)
at /gdal/ogr/ogrsf_frmts/miramon/ogrmiramondatasource.cpp:71
#5  0x76f2d268 in OGRMiraMonDriverOpen (poOpenInfo=0x7fffdd00)
at /gdal/ogr/ogrsf_frmts/miramon/ogrmiramondriver.cpp:87
#6  0x773d0819 in GDALDriver::Open (this=0x55640cb0, 
poOpenInfo=0x7fffdd00, bSetOpenOptions=false)
at /gdal/gcore/gdaldriver.cpp:116
#7  0x773e9980 in GDALOpenEx (pszFilename=0x55d53d50 
"/vsimem/test1067.pol", nOpenFlags=14,
papszAllowedDrivers=0x0, papszOpenOptions=0x0, papszSiblingFiles=0x0) at 
/gdal/gcore/gdaldataset.cpp:3745
#8  0x773d4be7 in GDALDriver::Delete (this=0x55640cb0, 
pszFilename=0x55d53d50 "/vsimem/test1067.pol")
at /gdal/gcore/gdaldriver.cpp:1645
#9  0xe6f0 in TestCreateLayer (poDriver=0x55640cb0, 
eGeomType=wkbLineString)
at /gdal/apps/test_ogrsf.cpp:1017
#10 0xef8f in TestCreate (poDriver=0x55640cb0, 
bFromAllDrivers=1) at /gdal/apps/test_ogrsf.cpp:1107
#11 0xbdb2 in ThreadFunctionInternal (psContext=0x7fffe400) at 
/gdal/apps/test_ogrsf.cpp:325
#12 0xbc71 in ThreadFunction (user_data=0x7fffe400) at 
/gdal/apps/test_ogrsf.cpp:283
#13 0xbac1 in main (nArgc=2, papszArgv=0x55645050) at 
/gdal/apps/test_ogrsf.cpp:233


-Mensaje original-
De: gdal-dev  En nombre de Abel Pau via 
gdal-dev
Enviado el: dilluns, 4 de març de 2024 10:42
Para: Even Rouault ; gdal-dev@lists.osgeo.org
Asunto: Re: [gdal-dev] Alpine, gcc 32-bit in Linux Build Actions

After some investigations, I've concluded that I was doing two things that I've 
improved lately:
1) Addressing a memory leak (in a non-typical case in my previous 
tests). CORRECTED
2) I was requesting an amount of memory suitable for ogr2ogr of large 
layers but not for numerous translations on a machine with limited memory. I've 
reduced the amount of memory required by /10. And now Alpine 32 bits is in 
green colour!

There are still some tests to review, but I'm optimistic about submitting a 
pull request soon!


-Mensaje original-
De: gdal-dev  En nombre de Abel Pau via 
gdal-dev Enviado el: divendres, 1 de març de 2024 16:18
Para: Even Rouault ; gdal-dev@lists.osgeo.org
Asunto: Re: [gdal-dev] Alpine, gcc 32-bit in Linux Build Actions

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 don't know how to debug in my Docker linux (only command line) with Cmake 
compiler...

I think I'll catch the problem. Sooner or later!

I've been there before (years ago with a big problem (not my fault)). Finally I 
win

-Mensaje original-
De: Even Rouault  Enviado el: divendres, 1 de març 
de 2024 16:12
Para: Abel Pau ; gdal-dev@lists.osgeo.org
Asunto: Re: [gdal-dev] Alpine, gcc 32-bit in Linux Build Actions

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

and then use "step", and "next" to single step and locate where this crashes. 
This is going to be a bit tedious...

(you might also want to modify slightly test_ogrsf so that this
TestCreateLayer() method exists early when !EQUAL(poDriver->GetDescription(), 
"miramon") to avoid debugging other
drivers)

You might install "ddd", as a GUI front-end for gdb, so that this is slightly 
more user friendly.

-- 

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

___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/

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

2024-03-04 Thread Abel Pau via gdal-dev 
After some investigations, I've concluded that I was doing two things that I've 
improved lately:
1) Addressing a memory leak (in a non-typical case in my previous 
tests). CORRECTED
2) I was requesting an amount of memory suitable for ogr2ogr of large 
layers but not for numerous translations on a machine with limited memory. I've 
reduced the amount of memory required by /10. And now Alpine 32 bits is in 
green colour!

There are still some tests to review, but I'm optimistic about submitting a 
pull request soon!


-Mensaje original-
De: gdal-dev  En nombre de Abel Pau via 
gdal-dev
Enviado el: divendres, 1 de març de 2024 16:18
Para: Even Rouault ; gdal-dev@lists.osgeo.org
Asunto: Re: [gdal-dev] Alpine, gcc 32-bit in Linux Build Actions

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 don't know how to debug in my Docker linux (only command line) with Cmake 
compiler...

I think I'll catch the problem. Sooner or later!

I've been there before (years ago with a big problem (not my fault)). Finally I 
win

-Mensaje original-
De: Even Rouault  Enviado el: divendres, 1 de març 
de 2024 16:12
Para: Abel Pau ; gdal-dev@lists.osgeo.org
Asunto: Re: [gdal-dev] Alpine, gcc 32-bit in Linux Build Actions

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

and then use "step", and "next" to single step and locate where this crashes. 
This is going to be a bit tedious...

(you might also want to modify slightly test_ogrsf so that this
TestCreateLayer() method exists early when !EQUAL(poDriver->GetDescription(), 
"miramon") to avoid debugging other
drivers)

You might install "ddd", as a GUI front-end for gdb, so that this is slightly 
more user friendly.

-- 

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

___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/gdal-dev
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/gdal-dev

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 don't know how to debug in my Docker linux (only command line) with Cmake 
compiler...

I think I'll catch the problem. Sooner or later!

I've been there before (years ago with a big problem (not my fault)). Finally I 
win

-Mensaje original-
De: Even Rouault  
Enviado el: divendres, 1 de març de 2024 16:12
Para: Abel Pau ; gdal-dev@lists.osgeo.org
Asunto: Re: [gdal-dev] Alpine, gcc 32-bit in Linux Build Actions

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

and then use "step", and "next" to single step and locate where this crashes. 
This is going to be a bit tedious...

(you might also want to modify slightly test_ogrsf so that this
TestCreateLayer() method exists early when !EQUAL(poDriver->GetDescription(), 
"miramon") to avoid debugging other
drivers)

You might install "ddd", as a GUI front-end for gdb, so that this is slightly 
more user friendly.

-- 

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

___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/gdal-dev

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

and then use "step", and "next" to single step and locate where this 
crashes. This is going to be a bit tedious...


(you might also want to modify slightly test_ogrsf so that this 
TestCreateLayer() method exists early when 
!EQUAL(poDriver->GetDescription(), "miramon") to avoid debugging other 
drivers)


You might install "ddd", as a GUI front-end for gdb, so that this is 
slightly more user friendly.


--

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

___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/gdal-dev

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 compiled like that:
cmake .. -DCMAKE_BUILD_TYPE=Debug
cmake --build .

So...

De: Even Rouault 
Enviado el: divendres, 1 de març de 2024 13:28
Para: Abel Pau ; gdal-dev@lists.osgeo.org
Asunto: Re: [gdal-dev] Alpine, gcc 32-bit in Linux Build Actions


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 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: Creation of /foo/test.pol should have failed.
INFO: MiraMonVector: CreateFeature() at line 780 succeeded but failed to assign 
FID to feature.
Killed

If I add –v to valgrint, same thing. Nothing more concrete
Same for gdb.

I’ll try some prints (or the log system) to see where exactly it crashes.


De: Even Rouault <mailto:even.roua...@spatialys.com>
Enviado el: divendres, 1 de març de 2024 11:43
Para: Abel Pau <mailto:a@creaf.uab.cat>; 
gdal-dev@lists.osgeo.org<mailto:gdal-dev@lists.osgeo.org>
Asunto: Re: [gdal-dev] Alpine, gcc 32-bit in Linux Build Actions


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
run

and hopefully it will crash and give you some hints

and/or

valgrind test_ogrsf -all_drivers

Even


Le 01/03/2024 à 11:29, Abel Pau via gdal-dev a écrit :
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 some new information to clarify myself?

test_ogr_basic_10
It’s this INFO message (that other drivers also give) a problem?
INFO: MiraMonVector: Creation of /foo\test.pol should have failed.

This message also appears in some other drivers.
INFO: MiraMonVector: CreateFeature() at line 780 succeeded but failed to assign 
FID to feature.

Al tests in Linux 
Builds<https://github.com/AbelPau/gdal/actions/runs/8101809119> (in Actions) 
are OK except Alpine, gcc 32-bit
MiraMonVector driver (the one I am testing) seems to be OK.
gcore/test_driver_metadata.py::test_metadata_dcap_yes[MiraMonVector] PASSED [ 
38%]
gcore/test_driver_metadata.py::test_metadata_openoptionlist[MiraMonVector] 
PASSED [ 40%]
gcore/test_driver_metadata.py::test_metadata_creationoptionslist[MiraMonVector] 
PASSED [ 42%]
gcore/test_driver_metadata.py::test_metadata_layer_creationoptionslist[MiraMonVector]
 PASSED [ 42%]
gcore/test_driver_metadata.py::test_metadata_creation_field_datatypes[MiraMonVector]
 PASSED [ 44%]
gcore/test_driver_metadata.py::test_metadata_creation_sub_field_datatypes[MiraMonVector]
 PASSED [ 46%]
gcore/test_driver_metadata.py::test_metadata_alter_geom_field_defn_flags[MiraMonVector]
 PASSED [ 47%]
gcore/test_driver_metadata.py::test_metadata_alter_field_defn_flags[MiraMonVector]
 PASSED [ 48%]
gcore/test_driver_metadata.py::test_metadata_creation_field_defn_flags[MiraMonVector]
 PASSED [ 48%]

But
2024-02-29T20:01:51.4283306Z ogr/ogr_basic_test.py::test_ogr_basic_10 FAILED
  [  1%]

=== FAILURES ===
__ test_ogr_basic_10 ___

Al some point: ERROR ret code = -6
But no more clues why.

Anyone can tell me how to explore this error?
I debugged this test in windows but all seems correct.
The program '[15680] test_ogrsf.exe' has exited with code 0 (0x0).

I finally installed a linux ubuntu:22.04  in a docker and I can do some things 
related to tests.
When I do
python3 -m pytest -vv -p no:sugar --color=no 
ogr/ogr_basic_test.py::test_ogr_basic_10

After a while this error appears.
So, why?
E INFO: OpenFileGDB: CreateFeature() at line 837 failed but without 
explicit error.
E INFO: TestCreate(DXF).
E INFO: DXF: Creation of /foo/test.
E ERROR ret code = -9
E   assert 'ERROR' not in 'INFO: TestCreate(PCIDSK).\nINFO: PCIDSK: 
Creation of /foo/test.pix should have failed.\nINFO: TestCreate

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 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: Creation of /foo/test.pol should have failed.

INFO: MiraMonVector: CreateFeature() at line 780 succeeded but failed 
to assign FID to feature.


Killed

If I add *–v*to valgrint, same thing. Nothing more concrete

Same for gdb.

I’ll try some prints (or the log system) to see where exactly it crashes.

*De:*Even Rouault 
*Enviado el:* divendres, 1 de març de 2024 11:43
*Para:* Abel Pau ; gdal-dev@lists.osgeo.org
*Asunto:* Re: [gdal-dev] Alpine, gcc 32-bit in Linux Build Actions

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
run

and hopefully it will crash and give you some hints

and/or

valgrind test_ogrsf -all_drivers

Even

Le 01/03/2024 à 11:29, Abel Pau via gdal-dev a écrit :

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 some new information to clarify myself?

*test_ogr_basic_10*

It’s this INFO message (that other drivers also give) a problem?

INFO: MiraMonVector: Creation of /foo\test.pol should have failed.

This message also appears in some other drivers.

INFO: MiraMonVector: CreateFeature() at line 780 succeeded but
failed to assign FID to feature.

Al tests in Linux Builds
<https://github.com/AbelPau/gdal/actions/runs/8101809119>(in
Actions) are OK except *Alpine, gcc 32-bit*

MiraMonVector driver (the one I am testing) seems to be OK.

gcore/test_driver_metadata.py::test_metadata_dcap_yes[MiraMonVector]
PASSED [ 38%]

gcore/test_driver_metadata.py::test_metadata_openoptionlist[MiraMonVector]
PASSED [ 40%]


gcore/test_driver_metadata.py::test_metadata_creationoptionslist[MiraMonVector]
PASSED [ 42%]


gcore/test_driver_metadata.py::test_metadata_layer_creationoptionslist[MiraMonVector]
PASSED [ 42%]


gcore/test_driver_metadata.py::test_metadata_creation_field_datatypes[MiraMonVector]
PASSED [ 44%]


gcore/test_driver_metadata.py::test_metadata_creation_sub_field_datatypes[MiraMonVector]
PASSED [ 46%]


gcore/test_driver_metadata.py::test_metadata_alter_geom_field_defn_flags[MiraMonVector]
PASSED [ 47%]


gcore/test_driver_metadata.py::test_metadata_alter_field_defn_flags[MiraMonVector]
PASSED [ 48%]


gcore/test_driver_metadata.py::test_metadata_creation_field_defn_flags[MiraMonVector]
PASSED [ 48%]

But

2024-02-29T20:01:51.4283306Z
ogr/ogr_basic_test.py::test_ogr_basic_10 FAILED
   [  1%]

=== FAILURES
===

__ test_ogr_basic_10
___

Al some point: ERROR ret code = -6

*But no more clues why.*

Anyone can tell me how to explore this error?

I debugged this test in windows but all seems correct.

The program '[15680] test_ogrsf.exe' has exited with code 0 (0x0).


I finally installed a linux ubuntu:22.04  in a docker and I can do
some things related to tests.

When I do

python3 -m pytest -vv -p no:sugar --color=no
ogr/ogr_basic_test.py::test_ogr_basic_10

After a while this error appears.

So, why?

E INFO: OpenFileGDB: CreateFeature() at line 837 failed
but without explicit error.

E INFO: TestCreate(DXF).

E INFO: DXF: Creation of /foo/test.

*E ERROR ret code = -9*

E   assert 'ERROR' not in 'INFO: TestCreate(PCIDSK).\nINFO:
PCIDSK: Creation of /foo/test.pix should have failed.\nINFO:
TestCreate(netCDF).\nINFO: netCDF: Creation of /foo/test.nc should
have failed.\nINFO: netCDF: Creation of /vsimem/test33.n

*Abel Pau Garcia*

*GIS developer*



https://www.creaf.cat/sites/default/files/creaf-signature.png

*a@creaf.uab.cat* <mailto:a@creaf.uab.cat>

*Let's chat on Teams!*
<https://teams.m

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: Creation of /foo/test.pol should have failed.
INFO: MiraMonVector: CreateFeature() at line 780 succeeded but failed to assign 
FID to feature.
Killed

If I add –v to valgrint, same thing. Nothing more concrete
Same for gdb.

I’ll try some prints (or the log system) to see where exactly it crashes.


De: Even Rouault 
Enviado el: divendres, 1 de març de 2024 11:43
Para: Abel Pau ; gdal-dev@lists.osgeo.org
Asunto: Re: [gdal-dev] Alpine, gcc 32-bit in Linux Build Actions


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
run

and hopefully it will crash and give you some hints

and/or

valgrind test_ogrsf -all_drivers

Even


Le 01/03/2024 à 11:29, Abel Pau via gdal-dev a écrit :
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 some new information to clarify myself?

test_ogr_basic_10
It’s this INFO message (that other drivers also give) a problem?
INFO: MiraMonVector: Creation of /foo\test.pol should have failed.

This message also appears in some other drivers.
INFO: MiraMonVector: CreateFeature() at line 780 succeeded but failed to assign 
FID to feature.

Al tests in Linux 
Builds<https://github.com/AbelPau/gdal/actions/runs/8101809119> (in Actions) 
are OK except Alpine, gcc 32-bit
MiraMonVector driver (the one I am testing) seems to be OK.
gcore/test_driver_metadata.py::test_metadata_dcap_yes[MiraMonVector] PASSED [ 
38%]
gcore/test_driver_metadata.py::test_metadata_openoptionlist[MiraMonVector] 
PASSED [ 40%]
gcore/test_driver_metadata.py::test_metadata_creationoptionslist[MiraMonVector] 
PASSED [ 42%]
gcore/test_driver_metadata.py::test_metadata_layer_creationoptionslist[MiraMonVector]
 PASSED [ 42%]
gcore/test_driver_metadata.py::test_metadata_creation_field_datatypes[MiraMonVector]
 PASSED [ 44%]
gcore/test_driver_metadata.py::test_metadata_creation_sub_field_datatypes[MiraMonVector]
 PASSED [ 46%]
gcore/test_driver_metadata.py::test_metadata_alter_geom_field_defn_flags[MiraMonVector]
 PASSED [ 47%]
gcore/test_driver_metadata.py::test_metadata_alter_field_defn_flags[MiraMonVector]
 PASSED [ 48%]
gcore/test_driver_metadata.py::test_metadata_creation_field_defn_flags[MiraMonVector]
 PASSED [ 48%]

But
2024-02-29T20:01:51.4283306Z ogr/ogr_basic_test.py::test_ogr_basic_10 FAILED
  [  1%]

=== FAILURES ===
__ test_ogr_basic_10 ___

Al some point: ERROR ret code = -6
But no more clues why.

Anyone can tell me how to explore this error?
I debugged this test in windows but all seems correct.
The program '[15680] test_ogrsf.exe' has exited with code 0 (0x0).

I finally installed a linux ubuntu:22.04  in a docker and I can do some things 
related to tests.
When I do
python3 -m pytest -vv -p no:sugar --color=no 
ogr/ogr_basic_test.py::test_ogr_basic_10

After a while this error appears.
So, why?
E INFO: OpenFileGDB: CreateFeature() at line 837 failed but without 
explicit error.
E INFO: TestCreate(DXF).
E INFO: DXF: Creation of /foo/test.
E ERROR ret code = -9
E   assert 'ERROR' not in 'INFO: TestCreate(PCIDSK).\nINFO: PCIDSK: 
Creation of /foo/test.pix should have failed.\nINFO: TestCreate(netCDF).\nINFO: 
netCDF: Creation of /foo/test.nc should have failed.\nINFO: netCDF: Creation of 
/vsimem/test33.n

Abel Pau Garcia
GIS developer
[https://www.creaf.cat/sites/default/files/creaf-signature.png]
a@creaf.uab.cat<mailto:a@creaf.uab.cat>
Let's chat on 
Teams!<https://teams.microsoft.com/l/chat/0/0?users=a@creaf.uab.cat>
Tel. +34 934814277
[https://www.creaf.cat/sites/default/files/so-en-signature.png]
[https://www.creaf.cat/sites/default/files/twitter-icon-signature.png]<https://twitter.com/CREAF_ecologia>[https://www.creaf.cat/sites/default/files/linkedin-icon-signature.png]<https://www.linkedin.com/company/1363052?trk=tyah&trkInfo=clickedVertical:company,clickedEntityId:1363052,idx:2-1-2,tarId:1465807877789,tas:creaf>[https://www.creaf.cat/sites/default/files/youtube-icon-signature.png]<https://www.youtube.com/c/creafecologia>[https://www.creaf.cat/sites/defa

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
run

and hopefully it will crash and give you some hints

and/or

valgrind test_ogrsf -all_drivers

Even


Le 01/03/2024 à 11:29, Abel Pau via gdal-dev a écrit :


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 some new information to clarify myself?

*test_ogr_basic_10*

It’s this INFO message (that other drivers also give) a problem?

INFO: MiraMonVector: Creation of /foo\test.pol should have failed.

This message also appears in some other drivers.

INFO: MiraMonVector: CreateFeature() at line 780 succeeded but failed 
to assign FID to feature.


Al tests in Linux Builds 
 (in Actions) 
are OK except *Alpine, gcc 32-bit*


MiraMonVector driver (the one I am testing) seems to be OK.

gcore/test_driver_metadata.py::test_metadata_dcap_yes[MiraMonVector] 
PASSED [ 38%]


gcore/test_driver_metadata.py::test_metadata_openoptionlist[MiraMonVector] 
PASSED [ 40%]


gcore/test_driver_metadata.py::test_metadata_creationoptionslist[MiraMonVector] 
PASSED [ 42%]


gcore/test_driver_metadata.py::test_metadata_layer_creationoptionslist[MiraMonVector] 
PASSED [ 42%]


gcore/test_driver_metadata.py::test_metadata_creation_field_datatypes[MiraMonVector] 
PASSED [ 44%]


gcore/test_driver_metadata.py::test_metadata_creation_sub_field_datatypes[MiraMonVector] 
PASSED [ 46%]


gcore/test_driver_metadata.py::test_metadata_alter_geom_field_defn_flags[MiraMonVector] 
PASSED [ 47%]


gcore/test_driver_metadata.py::test_metadata_alter_field_defn_flags[MiraMonVector] 
PASSED [ 48%]


gcore/test_driver_metadata.py::test_metadata_creation_field_defn_flags[MiraMonVector] 
PASSED [ 48%]


But

2024-02-29T20:01:51.4283306Z ogr/ogr_basic_test.py::test_ogr_basic_10 
FAILED    [  1%]


=== FAILURES 
===


__ test_ogr_basic_10 
___


Al some point: ERROR ret code = -6

*But no more clues why.*

Anyone can tell me how to explore this error?

I debugged this test in windows but all seems correct.

The program '[15680] test_ogrsf.exe' has exited with code 0 (0x0).


I finally installed a linux ubuntu:22.04  in a docker and I can do 
some things related to tests.


When I do

python3 -m pytest -vv -p no:sugar --color=no 
ogr/ogr_basic_test.py::test_ogr_basic_10


After a while this error appears.

So, why?

E INFO: OpenFileGDB: CreateFeature() at line 837 failed but 
without explicit error.


E INFO: TestCreate(DXF).

E INFO: DXF: Creation of /foo/test.

*E ERROR ret code = -9*

E   assert 'ERROR' not in 'INFO: TestCreate(PCIDSK).\nINFO: 
PCIDSK: Creation of /foo/test.pix should have failed.\nINFO: 
TestCreate(netCDF).\nINFO: netCDF: Creation of /foo/test.nc should 
have failed.\nINFO: netCDF: Creation of /vsimem/test33.n


*Abel Pau Garcia*

*GIS developer*



https://www.creaf.cat/sites/default/files/creaf-signature.png

*a@creaf.uab.cat* 

*Let's chat on Teams!* 



*Tel. +34 934814277*



https://www.creaf.cat/sites/default/files/so-en-signature.png

https://www.creaf.cat/sites/default/files/twitter-icon-signature.png 
https://www.creaf.cat/sites/default/files/linkedin-icon-signature.png 
https://www.creaf.cat/sites/default/files/youtube-icon-signature.png 
https://www.creaf.cat/sites/default/files/instagram-icon-signature.png 



*www.creaf.cat* *| **http://blog.creaf.cat* 





https://www.creaf.cat/sites/default/files/uab_logo_signatura.png

CREAF. Campus UAB. Edifici C. 08193 Bellaterra (Barcelona)


Before printing this electronic message, think about the environment.

http://www.creaf.uab.cat/_signatura/line.gif


___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/gdal-dev


--
http://www.spatialys.com
My software is free, but my time generally not.
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://l