On Thu, Mar 22, 2018 at 9:09 AM, Andres Freund <and...@anarazel.de> wrote: > Hi, > > On 2018-03-22 09:00:19 +1300, Thomas Munro wrote: >> 64 bit CPU, 32 bit OS. I didn't try Debian multi-arch i386 support on >> an amd64 system, but that's probably an easier way to do this if you >> already have one of those... > > Ah, then I think I might know what happend. Does it start to work if you > replace the auto-detected cpu with "x86"? I think what might happen is > that it generates 64bit code, because of the detected CPU name.
Hah, that makes sense. I tried setting cpu to "x86", and now it fails differently: Program terminated with signal SIGSEGV, Segmentation fault. #0 malloc_printerr (action=3, str=0xb7682d00 "free(): invalid pointer", ptr=0xae75f27b, ar_ptr=0xae700220 <llvm::SystemZ::GRX32BitRegClass>) at malloc.c:5036 5036 malloc.c: No such file or directory. (gdb) bt #0 malloc_printerr (action=3, str=0xb7682d00 "free(): invalid pointer", ptr=0xae75f27b, ar_ptr=0xae700220 <llvm::SystemZ::GRX32BitRegClass>) at malloc.c:5036 #1 0xb7593806 in _int_free (av=0xae700220 <llvm::SystemZ::GRX32BitRegClass>, p=0xae75f273, have_lock=0) at malloc.c:3905 #2 0xabd05cd8 in LLVMDisposeMessage () from /usr/lib/i386-linux-gnu/libLLVM-3.9.so.1 #3 0xae75100b in llvm_session_initialize () at llvmjit.c:636 #4 llvm_create_context (jitFlags=15) at llvmjit.c:136 #5 0xae75d3e9 in llvm_compile_expr (state=0x2616e60) at llvmjit_expr.c:132 #6 0x00650118 in ExecReadyExpr (state=state@entry=0x2616e60) at execExpr.c:627 #7 0x00652dd7 in ExecInitExpr (node=0x2666bb4, parent=0x261693c) at execExpr.c:144 ... -- Thomas Munro http://www.enterprisedb.com
