No worries 
Unfortunately I don’t see anything definitive in the traces - maybe something to do with gnutls, which is being accessed right before the crash. Could be some kind of incompatibility. Unless you see something probably it makes sense to create a debug build.
I’ll end up doing the debug build, ASAP. For now, I found this in dmesg, everytime I run the problematic build :
[21639.829126] traps: SlicerApp-real[15453] trap invalid opcode ip:7f8aa07fa1c8 sp:7ffce616fca8 error:0 in libitkgdcmcharls-5.0.so.1[7f8aa07e4000+84000]
It points out at least one library. ldd on this file does not reveal missing dependency.
Maybe the file is corrupted? invalid opcode indicates something pretty low level is going on.
Hi,
I built Slicer in debug mode and it does not crash surprisingly.
Then I built with RelWithDebInfo and this one does not start. I next ran
./Slicer --launch xterm
and in the new terminal
gdb ./bin/SlicerApp-real
Fatal Python error: initsite: Failed to import the site module
Traceback (most recent call last):
File “/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/bin/…/lib/Python/lib/python3.6/site.py”, line 553, in
main()
File “/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/bin/…/lib/Python/lib/python3.6/site.py”, line 539, in main
known_paths = addusersitepackages(known_paths)
File “/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/bin/…/lib/Python/lib/python3.6/site.py”, line 282, in addusersitepackages
user_site = getusersitepackages()
File “/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/bin/…/lib/Python/lib/python3.6/site.py”, line 258, in getusersitepackages
user_base = getuserbase() # this will also set USER_BASE
File “/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/bin/…/lib/Python/lib/python3.6/site.py”, line 248, in getuserbase
USER_BASE = get_config_var(‘userbase’)
File “/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/lib/Python/lib/python3.6/sysconfig.py”, line 601, in get_config_var
return get_config_vars().get(name)
File “/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/lib/Python/lib/python3.6/sysconfig.py”, line 550, in get_config_vars
_init_posix(_CONFIG_VARS)
File “/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/lib/Python/lib/python3.6/sysconfig.py”, line 421, in _init_posix
_temp = import(name, globals(), locals(), [‘build_time_vars’], 0)
ModuleNotFoundError: No module named ‘_sysconfigdata_m_linux_x86_64-linux-gnu’
It seems that Python in the Slicer tree is looking for an unknown module in non-debug builds. On this single machine at least.
I’ll be using the debug build, and hope for a fix.
Regards.
This information is very helpful. Have you tried to google for possible solutions?
For example, this one is interesting:
The problem is that user site packages are attempted to loaded (...user_site = getusersitepackages()...). They shouldn’t be loaded (see here).
Does any of the followings work?
./PythonSlicer./PythonSlicer -s./PythonSlicer -SDoes settings PYTHONNOUSERSITE=1 environment variable make any difference?
Can you investigate why user site packages loading is not prevented (by reviewing content and adding print statements to the .py files listed in the call stack)?
Well my Python knowledge is very scarce. In the --launch(ed) terminal, PythonSlicer {,-s,-S} works.
In that terminal, even launching ‘gdb’ without any argument generates the above mentioned Python errors.
PYTHONNOUSERSITE is already set to 1 in that terminal. Experimented with 0 to no avail.
Blindly, I unset PYTHONHOME, and then I could get a gdb prompt, with this console output :
Reading symbols from bin/SlicerApp-real…
(gdb) r
Starting program: /home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/bin/SlicerApp-real
[Thread debugging using libthread_db enabled]
Using host libthread_db library “/usr/lib/libthread_db.so.1”.
Traceback (most recent call last):
File “/usr/share/gdb/auto-load/usr/lib/libstdc++.so.6.0.26-gdb.py”, line 18, in
import gdb
File “/usr/share/gdb/python/gdb/init.py”, line 16, in
import traceback
File “/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/lib/Python/lib/python3.6/traceback.py”, line 5, in
import linecache
File “/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/lib/Python/lib/python3.6/linecache.py”, line 11, in
import tokenize
File “/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/lib/Python/lib/python3.6/tokenize.py”, line 33, in
import re
File “/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/lib/Python/lib/python3.6/re.py”, line 123, in
import sre_compile
File “/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/lib/Python/lib/python3.6/sre_compile.py”, line 17, in
assert _sre.MAGIC == MAGIC, “SRE module mismatch”
AssertionError: SRE module mismatch
Traceback (most recent call last):
File “/usr/share/gdb/auto-load/usr/lib/libglib-2.0.so.0.6000.6-gdb.py”, line 2, in
import gdb
File “/usr/share/gdb/python/gdb/init.py”, line 16, in
import traceback
File “/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/lib/Python/lib/python3.6/traceback.py”, line 5, in
import linecache
File “/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/lib/Python/lib/python3.6/linecache.py”, line 11, in
import tokenize
File “/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/lib/Python/lib/python3.6/tokenize.py”, line 33, in
import re
File “/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/lib/Python/lib/python3.6/re.py”, line 123, in
import sre_compile
File “/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/lib/Python/lib/python3.6/sre_compile.py”, line 17, in
assert _sre.MAGIC == MAGIC, “SRE module mismatch”
AssertionError: SRE module mismatchProgram received signal SIGILL, Illegal instruction.
Python Exception <class ‘NameError’> Installation error: gdb.execute_unwinders function is missing:
0x00007fffdf555ba5 in v3p_netlib_slamc2_ (Python Exception <class ‘NameError’> Installation error: gdb.execute_unwinders function is missing:
Python Exception <class ‘NameError’> Installation error: gdb.execute_unwinders function is missing:
beta=beta@entry=0x7fffffffcc48, t=t@entry=0x7fffffffcc40, rnd=rnd@entry=0x7fffffffcc60,
eps=eps@entry=0x7fffdf627884 , emin=emin@entry=0x7fffffffcc50, rmin=rmin@entry=0x7fffdf627880 , emax=0x7fffffffcc58,
rmax=0x7fffdf62787c ) at /home/arc/src/Slicer-SuperBuild/ITK/Modules/ThirdParty/VNL/src/vxl/v3p/netlib/blas/slamch.c:719
719 /home/arc/src/Slicer-SuperBuild/ITK/Modules/ThirdParty/VNL/src/vxl/v3p/netlib/blas/slamch.c: No such file or directory.
(gdb) bt
Python Exception <class ‘AssertionError’> SRE module mismatch:
#0 0x00007fffdf555ba5 in v3p_netlib_slamc2_ (beta=beta@entry=0x7fffffffcc48, t=t@entry=0x7fffffffcc40, rnd=rnd@entry=0x7fffffffcc60,
eps=eps@entry=0x7fffdf627884 , emin=emin@entry=0x7fffffffcc50, rmin=rmin@entry=0x7fffdf627880 , emax=0x7fffffffcc58,
rmax=0x7fffdf62787c ) at /home/arc/src/Slicer-SuperBuild/ITK/Modules/ThirdParty/VNL/src/vxl/v3p/netlib/blas/slamch.c:719
#1 0x00007fffdf5564b0 in v3p_netlib_slamch_ (cmach=cmach@entry=0x7fffdf612923 " ", cmach_len=cmach_len@entry=1)
at /home/arc/src/Slicer-SuperBuild/ITK/Modules/ThirdParty/VNL/src/vxl/v3p/netlib/blas/slamch.c:165
#2 0x00007fffdf5568b1 in v3p_netlib_slamch_init ()
at /home/arc/src/Slicer-SuperBuild/ITK/Modules/ThirdParty/VNL/src/vxl/v3p/netlib/blas/slamch.c:53
Python Exception <class ‘NameError’> Installation error: gdb.execute_unwinders function is missing:
#3 0x00007fffdf54c3f5 in v3p_netlib_initialize ()
at /home/arc/src/Slicer-SuperBuild/ITK/Modules/ThirdParty/VNL/src/vxl/v3p/netlib/v3p_netlib_init.c:19
Python Exception <class ‘NameError’> Installation error: gdb.execute_unwinders function is missing:
#4 0x00007ffff7fe279a in call_init.part () from /lib64/ld-linux-x86-64.so.2
Python Exception <class ‘NameError’> Installation error: gdb.execute_unwinders function is missing:
#5 0x00007ffff7fe28a1 in _dl_init () from /lib64/ld-linux-x86-64.so.2
Python Exception <class ‘NameError’> Installation error: gdb.execute_unwinders function is missing:
#6 0x00007ffff7fd413a in _dl_start_user () from /lib64/ld-linux-x86-64.so.2
Python Exception <class ‘NameError’> Installation error: gdb.execute_unwinders function is missing:
#7 0x0000000000000001 in ?? ()
Python Exception <class ‘NameError’> Installation error: gdb.execute_unwinders function is missing:
#8 0x00007fffffffd28d in ?? ()
Python Exception <class ‘NameError’> Installation error: gdb.execute_unwinders function is missing:
#9 0x0000000000000000 in ?? ()
Python Exception <class ‘NameError’> Installation error: gdb.execute_unwinders function is missing:
(gdb)
dmesg shows this error with libitkv3p_netlib :
[ 7052.275896] traps: SlicerApp-real[4907] trap invalid opcode ip:7f5e91312ba5 sp:7ffe51239fa0 error:0 in libitkv3p_netlib-5.0.so.1[7f5e912fe000+e4000]
I understand, perhaps wrongly, that the runtime error first occurs at
ITK/Modules/ThirdParty/VNL/src/vxl/v3p/netlib/blas/slamch.c:719
or at
ITK/Modules/ThirdParty/VNL/src/vxl/v3p/netlib/v3p_netlib_init.c:19
Please note that Slicer built in Debug mode runs normally. Slicer crashes when built in Release or in RelWithDebInfo modes only.
Regards.
There should be no need to change PYTHONHOME (it would just break everything). Instead, add print statements to show values of variables that control usage of user site packages to find out why getusersitepackages is called.
You may also try to clear out your user-specific site.py file (and parent folders) to confirm that it causes the Python startup failure.
I’m quite lost with Python. If I call _main() in lib/Python/lib/python3.6/sysconfig.py at line 421 to get some information, the output is :
$ gdb
Platform: “linux-x86_64”
Python version: “3.7”
Current installation scheme: “posix_prefix”Paths:
data = “/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/lib/Python”
include = “/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/lib/Python/include/python3.7m”
platinclude = “/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/lib/Python/include/python3.7m”
platlib = “/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/lib/Python/lib/python3.7/site-packages”
platstdlib = “/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/lib/Python/lib/python3.7”
purelib = “/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/lib/Python/lib/python3.7/site-packages”
scripts = “/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/lib/Python/bin”
stdlib = “/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/lib/Python/lib/python3.7”Variables:
abiflags = “m”
base = “/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/lib/Python”
exec_prefix = “/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/lib/Python”
installed_base = “/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/lib/Python”
installed_platbase = “/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/lib/Python”
platbase = “/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/lib/Python”
prefix = “/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/lib/Python”
projectbase = “/usr/bin”
py_version = “3.7.4”
py_version_nodot = “37”
py_version_short = “3.7”
Fatal Python error: initsite: Failed to import the site module
Traceback (most recent call last):
File “/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/bin/…/lib/Python/lib/python3.6/site.py”, line 553, in
main()
File “/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/bin/…/lib/Python/lib/python3.6/site.py”, line 539, in main
known_paths = addusersitepackages(known_paths)
File “/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/bin/…/lib/Python/lib/python3.6/site.py”, line 282, in addusersitepackages
user_site = getusersitepackages()
File “/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/bin/…/lib/Python/lib/python3.6/site.py”, line 258, in getusersitepackages
user_base = getuserbase() # this will also set USER_BASE
File “/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/bin/…/lib/Python/lib/python3.6/site.py”, line 248, in getuserbase
USER_BASE = get_config_var(‘userbase’)
File “/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/lib/Python/lib/python3.6/sysconfig.py”, line 602, in get_config_var
return get_config_vars().get(name)
File “/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/lib/Python/lib/python3.6/sysconfig.py”, line 551, in get_config_vars
_init_posix(_CONFIG_VARS)
File “/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/lib/Python/lib/python3.6/sysconfig.py”, line 422, in _init_posix
_temp = import(name, globals(), locals(), [‘build_time_vars’], 0)
ModuleNotFoundError: No module named ‘_sysconfigdata_m_linux_x86_64-linux-gnu’
Here system Python 3.7 is being called.
$ env |grep PYTHON
PYTHONNOUSERSITE=1
PYTHONPATH=/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/bin/…/lib/Slicer-4.11:/home/user/programs/Test/Sli
cer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/bin/…/lib/Slicer-4.11/qt-scripted-modules:/home/user/programs/Test/Slicer-4.11.0-2019-08-
22-linux-amd64-RelWithDebInfo-O2/bin/…/lib/Slicer-4.11/qt-loadable-modules:/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelW
ithDebInfo-O2/bin/…/lib/vtkTeem:/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/bin/…/bin/Python:/home/user/
programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/bin/…/lib/Slicer-4.11/qt-loadable-modules/Python:/home/user/programs/Tes
t/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/bin/…/lib/Python/lib/python3.6:/home/user/programs/Test/Slicer-4.11.0-2019-08-22-lin
ux-amd64-RelWithDebInfo-O2/bin/…/lib/Python/lib/python3.6/lib-dynload:/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDe
bInfo-O2/bin/…/lib/Python/lib/python3.6/site-packages:/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/bin/…/
./lib/Slicer-4.11/python3.6/site-packages
PYTHONHOME=/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/bin/…/lib/Python
$ env |grep python
PYTHONPATH=/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/bin/…/lib/Slicer-4.11:/home/user/programs/Test/Sli
cer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/bin/…/lib/Slicer-4.11/qt-scripted-modules:/home/user/programs/Test/Slicer-4.11.0-2019-08-
22-linux-amd64-RelWithDebInfo-O2/bin/…/lib/Slicer-4.11/qt-loadable-modules:/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelW
ithDebInfo-O2/bin/…/lib/vtkTeem:/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/bin/…/bin/Python:/home/user/
programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/bin/…/lib/Slicer-4.11/qt-loadable-modules/Python:/home/user/programs/Tes
t/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/bin/…/lib/Python/lib/python3.6:/home/user/programs/Test/Slicer-4.11.0-2019-08-22-lin
ux-amd64-RelWithDebInfo-O2/bin/…/lib/Python/lib/python3.6/lib-dynload:/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDe
bInfo-O2/bin/…/lib/Python/lib/python3.6/site-packages:/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/bin/…/
./lib/Slicer-4.11/python3.6/site-packages
LD_LIBRARY_PATH=/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/bin/…/bin:/home/user/programs/Test/Slicer-4.1
1.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/bin/…/lib/Slicer-4.11:/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebIn
fo-O2/bin/…/lib/Slicer-4.11/cli-modules:/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/bin/…/lib/Slicer-4.1
1/qt-loadable-modules:…/lib/Slicer-4.11/qt-loadable-modules:/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/b
in/…/lib/Python/lib:/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/bin/…/lib/Teem-1.12.0:/home/user/program
s/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/bin/…/lib/PythonQt:/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd6
4-RelWithDebInfo-O2/bin/…/lib/Python/lib/python3.6/site-packages/numpy/core:/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-Rel
WithDebInfo-O2/bin/…/lib/Python/lib/python3.6/site-packages/numpy/lib
$ echo $PATH
/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/bin/…/bin:/home/user/programs/Test/Slicer-4.11.0-2019-08-22-l
inux-amd64-RelWithDebInfo-O2/bin/…/lib/Slicer-4.11/cli-modules:/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O
2/bin/…/lib/Slicer-4.11/qt-loadable-modules:/home/user/.bin:/bin:/usr/bin:/usr/local/bin:/usr/local/sbin:/usr/lib/jvm/default/bin:/usr/bin/si
te_perl:/usr/bin/vendor_perl:/usr/bin/core_perl
Can’t know how to interpret all these.
Trying with lldb :
$ lldb ./bin/SlicerApp-real
(lldb) target create “./bin/SlicerApp-real”
Current executable set to ‘./bin/SlicerApp-real’ (x86_64).
(lldb) r
Process 13686 launched: ‘/home/user/programs/Test/Slicer-4.11.0-2019-08-22-linux-amd64-RelWithDebInfo-O2/bin/SlicerApp-real’ (x86_64)
Process 13686 stopped
- thread #1, name = ‘SlicerApp-real’, stop reason = signal SIGILL: illegal instruction operand
frame #0: 0x00007fffdf555ba5 libitkv3p_netlib-5.0.so.1`v3p_netlib_slamc2_(beta=0x00007fffffffc0a8, t=0x00007fffffffc0a0, rnd=0x00007fffffffc0c0, eps=0x00007fffdf627884, emin=0x00007fffffffc0b0, rmin=0x00007fffdf627880, emax=0x00007fffffffc0b8, rmax=0x00007fffdf62787c) at slamch.c:719:11
(lldb) bt- thread #1, name = ‘SlicerApp-real’, stop reason = signal SIGILL: illegal instruction operand
- frame #0: 0x00007fffdf555ba5 libitkv3p_netlib-5.0.so.1
v3p_netlib_slamc2_(beta=0x00007fffffffc0a8, t=0x00007fffffffc0a0, rnd=0x00007fffffffc0c0, eps=0x00007fffdf627884, emin=0x00007fffffffc0b0, rmin=0x00007fffdf627880, emax=0x00007fffffffc0b8, rmax=0x00007fffdf62787c) at slamch.c:719:11 frame #1: 0x00007fffdf5564b0 libitkv3p_netlib-5.0.so.1v3p_netlib_slamch_(cmach=" ", cmach_len=) at slamch.c:165:9
frame #2: 0x00007fffdf54c3f5 libitkv3p_netlib-5.0.so.1v3p_netlib_initialize at v3p_netlib_init.c:19:5 frame #3: 0x00007ffff7fe279a ld-2.29.socall_init.part.0 + 154
frame #4: 0x00007ffff7fe28a1 ld-2.29.so_dl_init + 129 frame #5: 0x00007ffff7fd413a ld-2.29.so_dl_start_user + 50
I think we run into the same problem on a very old computer (with Intel Core i7-3770 CPU) running Windows 10.
Slicer does not start but instead this error is shown in a popup:
The application was unable to start correctly (0xc0000142). Click OK to close the application
Windows application log tells that it is an exception 0xc000001d (Illegal instruction) in ITKIOGDCM-5.1.dll. Attaching a debugger and looking at the disassembly I found that indeed there was an shlx instruction where the exception was thrown, which is a BMI2 instruction that is not supported in 3rd-generation (3xxx, Ivy Bridge) CPUs but only in 4th generation (4xxx, Haswell) and later.
@chir.set Can you confirm that you had this problem on a 3rd-generation CPU?
We should either change build options to disable using BMI2 instruction set or check CPU type in the launcher and show a warning if non-compatible CPU is found. I’ve created an issue for this to make sure we follow up: https://issues.slicer.org/view.php?id=4712
@lassoan I wonder if this the same/similar issue I have been encountering our old Sandy Bridge (Xeon E5-1620) computers that were recently updated to Windows 10 from Windows 7? Slicer preview versions used to work fine, and now getting and error message
Is there a work around? We really don’t toss them out as they are fairly usable computers.
Yes, it’s exactly the same error.
I would tend towards dropping support for these 6-8 years old computers. It’s not just the CPU instruction set but graphics card features are very limited, too (VTK’s OpenGL2 backend is not compatible with these old systems anyway).
himm. Actually they have all 1080Ti on them, as they have discrete GPUs that we can upgrade (as the power supply permitting).
It’s an old AMD Phenom II X6 1100T CPU. It has 20+ instruction sets missing compared to recent CPUs.
However, Slicer build and runs with the following tuning :
-march=amdfam10 -mtune=amdfam10 -mno-sse4.1 -mno-sse4.2 (CFLAGS, CXXFLAGS, ADDITIONAL_CXX_FLAGS)
The funny part is that when built with GCC 9.1, it crashes when reading the first DICOM file. I can get the backtrace later on if it’s of importance.
But Slicer just behaves normally when built with clang 8, using the same options. I gave it a blast today and it was rock solid. For how long ? I can also just change my work machine or the CPU, but that’s not scheduled for now.
Regards.
But the build itself can be tuned ! Dropping support won’t help anyone downloading binaries from your repository. The rationale of doing the extra work to drop support for old CPUs is not that clear.
We have a few options:
C is the easiest to do (we are already doing it), but A or B would be of course better.
Probably disabling recent instruction sets would not cause significant performance degradation, so if someone prepared a pull request with the necessary compilation flag changes then we would integrate them.
These are my observations with today’s nightly :
Win 10 + E5-1620 gives the stated error.
Centos 7.6 + E5-2690 works fine.
(I will report on the Centos 7.6 + E5-1620 combination tomorrow).
These two CPUs are from the same generation. Are optimization flags OS specific?
Even worse, they are compiler-specific. It should be possible to find the right set of options for each toolchain but it may require a lot of iterations. By the time we get everything right (safely work on most systems but not to degrade performance on current systems), most of the old computers may be decommissioned.
I’ve checked recent ITK changes and maybe they messed up something there that can be reverted without too much pain. I’ve reported the issue to their forum.
Did the discussion on ITK forum conclude for a course of action?
I’m testing a solution (setting ITK_*_OPTIMIZATION_FLAGS to empty in Slicer superbuild). Once I confirm that it works, I’ll send a pull request. Probably tomorrow.
Confirmed the fix works on Windows. Commited in rev28520.