@ptrblck
I installed gdb 11.1 on the remote Linux node. If I run gdb commands below
gdb python3
r -c "import torch"
bt

I got the following output:

Starting program: /usr/bin/python3 -c “import torch”
[Thread debugging using libthread_db enabled]
Using host libthread_db library “/lib/x86_64-linux-gnu/libthread_db.so.1”.
[Detaching after fork from child process 2451545]
[New Thread 0x7fff09280640 (LWP 2451546)]
[New Thread 0x7fff08a7f640 (LWP 2451547)]
[New Thread 0x7fff0027e640 (LWP 2451548)]
[New Thread 0x7ffeffa7d640 (LWP 2451549)]
Thread 3 “python3” received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fff08a7f640 (LWP 2451547)]
0x0000000000000000 in ?? ()
(gdb) bt
#0 0x0000000000000000 in ?? ()
#1 0x00007fff09e23760 in blas_memory_alloc ()
from /usr/local/lib/python3.8/dist-packages/numpy/core/…/…/numpy.libs/libopenblasp-r0-09e95953.3.13.so
#2 0x00007fff09e23f24 in blas_thread_server ()
from /usr/local/lib/python3.8/dist-packages/numpy/core/…/…/numpy.libs/libopenblasp-r0-09e95953.3.13.so
#3 0x00007ffff7f90590 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#4 0x00007ffff7d0f223 in clone () from /lib/x86_64-linux-gnu/libc.so.6
(gdb)

Can we find out any clue of the segfault? Please let me know what I need to do next to probe the problem. Thanks.