This code segfaults:

LLVMDoubleVisitor v1;
v1.init({x, y}, *r);
LLVMDoubleVisitor v2;
v1 = v2;

Test case to reproduce:

• test: master...lkeegan:symengine:reproduce_llvm_segfault
• stacktrace: https://github.com/lkeegan/symengine/actions/runs/7020980960/job/19101975785

From the stacktrace I think this is a bug in LLVM and not in symengine, but maybe the simplest solution would be for symengine to use a unique_ptr instead of a shared_ptr to store llvm::LLVMContext and llvm::ExecutionEngine. This would disable the above problematic copy constructor.