Re: [gdal-dev] core dump on dir info

2024-02-06 Thread Michael Sumner via gdal-dev
I don't understand how jammy is "old" when the full build is itself using "BASE_IMAGE=ubuntu:22.04" But, I'm out of my depth in these emails and trying to learn, thanks! Cheers, Mike On Wed, 7 Feb 2024, 00:46 Javier Jimenez Shaw, wrote: > Could you set up your VMs to include those SSE instr

Re: [gdal-dev] core dump on dir info

2024-02-06 Thread Laurențiu Nicola via gdal-dev
On Tue, Feb 6, 2024, at 16:04, Even Rouault via gdal-dev wrote: > Le 06/02/2024 à 14:46, Javier Jimenez Shaw a écrit : > I remember older VirtualBox versions indeed had issues to propage AVX to > guest, but I believed that has been fixed now. I'm not aware of issues > with SSEx not being propagat

Re: [gdal-dev] core dump on dir info

2024-02-06 Thread Even Rouault via gdal-dev
Le 06/02/2024 à 14:46, Javier Jimenez Shaw a écrit : Could you set up your VMs to include those SSE instructions? I remember older VirtualBox versions indeed had issues to propage AVX to guest, but I believed that has been fixed now. I'm not aware of issues with SSEx not being propagate. I thi

Re: [gdal-dev] core dump on dir info

2024-02-06 Thread Javier Jimenez Shaw via gdal-dev
Could you set up your VMs to include those SSE instructions? I think that keeping VMs that "old" configured is a source of problems using pre-compiled binaries. The same way GDAL updates dependencies of compilers and other libraries to something more modern (but not too modern), those SSE instructi

Re: [gdal-dev] core dump on dir info

2024-02-05 Thread Michael Sumner via gdal-dev
yes, jammy VM on openstack is the host (and is where I run pretty much everything, though will increasingly use AWS). Thanks for the note, I'll try on other systems too. We need a security-allow set for vsicurl to work so if there are other little details I'll be keen to flush them out. Cheers, M

Re: [gdal-dev] core dump on dir info

2024-02-04 Thread Javier Jimenez Shaw via gdal-dev
Hi Mike Out of curiosity, are run running it in a virtual machine? A few year ago I had problems running a program in a virtual machine (virtualbox, but I read it happens in others) due to a missing SSE instruction. The solution there was to "enable" the missing instructions in the virtual machine

Re: [gdal-dev] core dump on dir info

2024-02-04 Thread Michael Sumner via gdal-dev
Excellent, thanks Even - confirmed at my end and on my original use-case. Cheers, Mike On Mon, Feb 5, 2024 at 12:04 PM Even Rouault wrote: > ghcr.io/osgeo/gdal:ubuntu-full-latest has been regenerated with the > rebuild of TileDB without AVX2. I've also enabled the > drivers-with-external-depe

Re: [gdal-dev] core dump on dir info

2024-02-04 Thread Even Rouault via gdal-dev
ghcr.io/osgeo/gdal:ubuntu-full-latest has been regenerated with the rebuild of TileDB without AVX2. I've also enabled the drivers-with-external-depencies-built-as-plugin GDAL build mode, so it is easy to just remove a given plugin by deleting the corresponding .so in /usr/lib/x86_64-linux-gnu/g

Re: [gdal-dev] core dump on dir info

2024-02-04 Thread Michael Sumner via gdal-dev
indeed there's no avx2: cat /proc/cpuinfo|grep sse|head -n 1 flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm rep_good nopl cpuid extd_apicid tsc_known_freq pni pclmulqdq ssse3 fma cx16

Re: [gdal-dev] core dump on dir info

2024-02-04 Thread Even Rouault via gdal-dev
ok, so I believe this is the AVX2 issue I was talking about, as I realize that enabling AVX2 is the default mode when TileDB is built from source (which the Docker image does), and must be explicitly disabled with "./bootstrap --disable-avx2" (I've just changed the build recipe to include that,

Re: [gdal-dev] core dump on dir info

2024-02-03 Thread Michael Sumner via gdal-dev
skipping TileDB does fix: ogr2ogr /tmp/newdir https://github.com/SymbolixAU/geojsonsf/raw/master/inst/examples/geo_melbourne.geojson -f "ESRI Shapefile" export GDAL_SKIP=TileDB ogrinfo /tmp/newdir/ INFO: Open of `/tmp/newdir/' using driver `ESRI Shapefile' successful. 1: geo_melbourne (Polyg

Re: [gdal-dev] core dump on dir info

2024-02-03 Thread Even Rouault via gdal-dev
- When it crashes under gdb, type "thread apply all bt" to get the stack trace of all threads - I suspect there is a connection with https://github.com/OSGeo/gdal/pull/9170 , but that pull request wouldn't help here as "/tmp/newdir" could be a valid connection to TileDB - how did you get Til

Re: [gdal-dev] core dump on dir info

2024-02-02 Thread Michael Sumner via gdal-dev
Thanks Even, so there's something about tiledb under gdb (or maybe I am mangling the context, I will try variants of the host I'm using). Run with valgrind included below. gdb --args ogrinfo /tmp/newdir/ ... (gdb) run Starting program: /usr/local/bin/ogrinfo /tmp/newdir/ [Thread debugging using l

Re: [gdal-dev] core dump on dir info

2024-02-02 Thread Even Rouault via gdal-dev
Michael, I'm wondering if there not might be something wrong with your build or runtime environment. Or there's something subtle, because that works fine for me with my dev build or in the ghcr.io/osgeo/gdal:alpine-normal-3.8.3 Docker image Try running "valgrind ogrinfo /tmp/newdir/" or "gdb

[gdal-dev] core dump on dir info

2024-02-02 Thread Michael Sumner via gdal-dev
I'm getting Illegal instruction / core dumped on ogrinfo of a directory: ogr2ogr /tmp/newdir https://github.com/SymbolixAU/geojsonsf/raw/master/inst/examples/geo_melbourne.geojson -f "ESRI Shapefile" ogrinfo /tmp/newdir/ Illegal instruction (core dumped) I've worked back through some docker imag