Hi @nkavokine @parcollet,
I tried to run a basic multiorbital, static interaction example and run into segmentation faults. This example is part of the triqs benchmarks (https://github.com/TRIQS/benchmarks/tree/master/Dimer) and runs perfectly fine with cthyb with the delta_interface, and with the old ctseg. I modified the example to use only density-density type interactions, and removed the off-diag onsite hoppings.
I created a backtrace and get slightly different backtraces for a run with Hartree_shift on (local levels) or off:
However, both seem to be related to some wrong dimensions handed over to detmanip. Before I start digging I thought I ask you whether you have an idea. Something must go wrong in util.hpp when calling something in detmanip. The value handed over seems to be very wrong 1154334476675265717 .
The branch I created runs automatically a test that reproduces the error.
Hi @nkavokine @parcollet, I tried to run a basic multiorbital, static interaction example and run into segmentation faults. This example is part of the triqs benchmarks (https://github.com/TRIQS/benchmarks/tree/master/Dimer) and runs perfectly fine with cthyb with the delta_interface, and with the old ctseg. I modified the example to use only density-density type interactions, and removed the off-diag onsite hoppings.
I created a backtrace and get slightly different backtraces for a run with Hartree_shift on (local levels) or off:
Full backtraces: lldb_bt.txt lldb_bt_hartree_shift.txt
However, both seem to be related to some wrong dimensions handed over to detmanip. Before I start digging I thought I ask you whether you have an idea. Something must go wrong in
util.hpp
when calling something in detmanip. The value handed over seems to be very wrong1154334476675265717
.The branch I created runs automatically a test that reproduces the error.