Hi Sandro.
I digged a bit more and it seems a bad interaction with
libopenblas0-pthread (in my case it gets installed by cdo package, but
it's a largely used lib, IIUC):
# gdb /usr/bin/python3 core
GNU gdb (Debian 10.1-1.7) 10.1.90.20210103-git
Copyright (C) 2021 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/python3...
(No debugging symbols found in /usr/bin/python3)
[New LWP 314439]
[New LWP 314432]
[New LWP 314434]
[New LWP 314435]
[New LWP 314433]
[New LWP 314436]
[New LWP 314438]
[New LWP 314437]
[New LWP 314440]
[New LWP 314429]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `python3'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x0000000000000000 in ?? ()
[Current thread is 1 (Thread 0x7f6e9d75e700 (LWP 314439))]
(gdb) bt
#0 0x0000000000000000 in ?? ()
#1 0x00007f6ed15c9709 in blas_memory_alloc () from
/usr/lib/x86_64-linux-gnu/libopenblas.so.0
#2 0x00007f6ed15c9f04 in ?? () from
/usr/lib/x86_64-linux-gnu/libopenblas.so.0
#3 0x00007f6ed42e1ea7 in start_thread (arg=<optimized out>) at
pthread_create.c:477
#4 0x00007f6ed4074def in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
I get the same segfault (NULL access in blas_memory_alloc) when
installing/running octave after installing cdo.
Can the bug be reopened and rerouted to libopenblas0 ?
Il 05/10/2021 05:03, Debian Bug Tracking System ha scritto:
This is an automatic notification regarding your Bug report
which was filed against the python3-numpy package:
#995454: python3-numpy: segfault and core dump with a simple "import numpy"
It has been closed by Sandro Tosi <mo...@debian.org>.
Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Sandro Tosi
<mo...@debian.org> by
replying to this email.
--
Diego Zuccato
DIFA - Dip. di Fisica e Astronomia
Servizi Informatici
Alma Mater Studiorum - Università di Bologna
V.le Berti-Pichat 6/2 - 40127 Bologna - Italy
tel.: +39 051 20 95786
