"Segmentation fault (core dumped)" error

build
#1

Dear all,

I build the source from GitHub in Windows10’s Ubuntu bash.
After “cmake & make”, “ctest” shows all tests are failed. And after “make install”, I try to run a H2O SCF example but get “Segmentation fault (core dumped)” error.
I can’t finger out the problem. Below is the cmake command.

cmake -H. -Bbuild
-DCMAKE_INSTALL_PREFIX="/home/jack/software/psi4"
-DCMAKE_PREFIX_PATH="/home/jack/software/psi4/external"
-DLAPACK_LIBRARIES="/usr/lib"
-DBUILD_SHARED_LIBS=ON

If you need more information, please let me know. Thank you in advance.

#2

What is CMAKE_PREFIX_PATH pointing to as you’re using it? Did the make succeed? What’s ldd stage/${CMAKE_INSTALL_PREFIX}/lib/psi4/core.so ? Are you connecting those lines in the cmake command with \ for line continuation if they’re on separate lines? What’s the output of the cmake configuation? Does psi4 --version work?

#3

The CMAKE_PREFIX_PATH is given as [psi4/external] which I had shown.
make is succeed, it hadn’t given error message at least.

ldd ./lib/psi4/core.so
linux-vdso.so.1 => (0x00007fffcb752000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f2f6b650000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f2f6b2c0000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f2f6afa0000)
libgomp.so.1 => /usr/lib/x86_64-linux-gnu/libgomp.so.1 (0x00007f2f6ad70000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f2f6ab50000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f2f6a920000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f2f6a550000)
/lib64/ld-linux-x86-64.so.2 (0x00007f2f6ea00000)

I do add \ at lines’ end.
Sorry, I don’t know how to find output of cmake configuration as it’s days ago.

psi4 --version
forrtl: error (69): process interrupted (SIGINT)
Image PC Routine Line Source
libpcm.so.1 00007FB49250CA15 Unknown Unknown Unknown
libpcm.so.1 00007FB49250A637 Unknown Unknown Unknown
libpcm.so.1 00007FB492422F32 Unknown Unknown Unknown
libpcm.so.1 00007FB492422D86 Unknown Unknown Unknown
libpcm.so.1 00007FB4923F138D Unknown Unknown Unknown
libpcm.so.1 00007FB4923F4FA7 Unknown Unknown Unknown
libpthread.so.0 00007FB49D101390 Unknown Unknown Unknown
ld-linux-x86-64.s 00007FB49D81B327 Unknown Unknown Unknown
ld-linux-x86-64.s 00007FB49D805767 Unknown Unknown Unknown
ld-linux-x86-64.s 00007FB49D808BD5 Unknown Unknown Unknown
ld-linux-x86-64.s 00007FB49D815577 Unknown Unknown Unknown
ld-linux-x86-64.s 00007FB49D810564 Unknown Unknown Unknown
ld-linux-x86-64.s 00007FB49D814DA9 Unknown Unknown Unknown
libdl.so.2 00007FB49CEE0F09 Unknown Unknown Unknown
ld-linux-x86-64.s 00007FB49D810564 Unknown Unknown Unknown
libdl.so.2 00007FB49CEE1571 Unknown Unknown Unknown
libpython3.5m.so. 00007FB49D490A53 Unknown Unknown Unknown
libpython3.5m.so. 00007FB49D46C287 Unknown Unknown Unknown
libpython3.5m.so. 00007FB49D46906F Unknown Unknown Unknown
…

lots of this Unknown.

Thanks for your help.

#4

I meant “what do you have installed at the location pointed to by CMAKE_PREFIX_PATH and where (package manager, personal compilation, etc.) did you get it?”. Are your lapack libraries static that they don’t show up in ldd? You’re telling it to build dynamic libraries and not telling it to build pcmsolver, but pcm isn’t showing up in ldd yet the error message is referencing libpcm.so.

Your circumstances strike me as strange, as if you’ve got more than one psi4 around or are mixing packages from multiple sources.