[GRASS-dev] segmentation fault with temporal commands

Markus Metz markus.metz.giswork at gmail.com
Mon Jul 30 05:28:34 PDT 2018


On Mon, Jul 30, 2018 at 1:37 PM, Markus Neteler <neteler at osgeo.org> wrote:
>
> Hi again,
>
> On Mon, Jul 30, 2018 at 1:05 PM, Markus Neteler <neteler at osgeo.org> wrote:
> ...
> > Thread 1 "python" received signal SIGSEGV, Segmentation fault.
> > 0x00007fffd7ac305b in blas_shutdown () from /lib64/libopenblaso.so.0
> > (gdb) bt full
> > #0  0x00007fffd7ac305b in blas_shutdown () from /lib64/libopenblaso.so.0
> > No symbol table info available.
> > #1  0x00007fffd788f015 in gotoblas_quit () from /lib64/libopenblaso.so.0
> > No symbol table info available.
> > #2  0x00007ffff7de58e6 in _dl_fini () from /lib64/ld-linux-x86-64.so.2
> > No symbol table info available.
> > #3  0x00007ffff6c4466c in __run_exit_handlers () from /lib64/libc.so.6
> > No symbol table info available.
> > #4  0x00007ffff6c4479c in exit () from /lib64/libc.so.6
> > No symbol table info available.
> > #5  0x00007ffff6c2e192 in __libc_start_main () from /lib64/libc.so.6
> > No symbol table info available.
> > #6  0x000055555555484a in _start ()
> > No symbol table info available.
> > (gdb)
> ...
> > Something is pulling in BLAS/openMP, though.
>
> Of course GDAL comes to mind:
>
> ldd `which gdalinfo` | grep openbla
>     libopenblaso.so.0 => /lib64/libopenblaso.so.0 (0x00007f4058bdc000)
>     libopenblasp.so.0 => /lib64/libopenblasp.so.0 (0x00007f4050b9f000)
>
> So, could it be related to lib/raster/* and GDAL related calls? I am
> not sure how to debug further.

It could also be python/numpy...

Markus M
>
> Markus
> _______________________________________________
> grass-dev mailing list
> grass-dev at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20180730/ee9c48d9/attachment.html>


More information about the grass-dev mailing list