Re: Query crash with 15.5 on debian bookworm/armv8

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Clemens Eisserer <linuxhippy(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Query crash with 15.5 on debian bookworm/armv8
Date: 2023-12-25 22:53:06
Message-ID: 1916830.1703544786@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Clemens Eisserer <linuxhippy(at)gmail(dot)com> writes:
> Program received signal SIGSEGV, Segmentation fault.
> 0x0000007fe5e6a9f0 in ?? () from /lib/aarch64-linux-gnu/libLLVM-14.so.1
> (gdb) bt full
> #0 0x0000007fe5e6a9f0 in ?? () from /lib/aarch64-linux-gnu/libLLVM-14.so.1
> No symbol table info available.
> #1 0x0000007fe59bb49c in llvm::raw_ostream::write(char const*,
> unsigned long) () from /lib/aarch64-linux-gnu/libLLVM-14.so.1
> No symbol table info available.

FWIW, since this crash is inside LLVM you could presumably dodge the bug
by setting "jit" to off.

As for an actual fix, perhaps a newer version of LLVM is needed?
I don't see a problem testing this query on my RPI with Ubuntu 23.10
(LLVM 16).

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Laurence Parry 2023-12-26 14:15:34 Logical replication stall on box type with REPLICA IDENTITY FULL due to lack of exact equality
Previous Message Adrian Klaver 2023-12-25 22:33:31 Re: Query crash with 15.5 on debian bookworm/armv8