From: | "Tom Turelinckx" <pgbf(at)twiska(dot)com> |
---|---|
To: | "Alexander Lakhin" <exclusion(at)gmail(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: RISC-V animals sporadically produce weird memory-related failures |
Date: | 2024-12-02 15:25:56 |
Message-ID: | 75b3a85a-8b07-4722-9f4b-c332d2ddecb0@app.fastmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi Alexander,
On Mon, Dec 2, 2024, at 2:00 PM, Alexander Lakhin wrote:
> These crashes are hardly related to code changes, so maybe there are
> platform-specific issues still...
I naively assumed that because llvm and clang are available in Trixie on riscv64 that I could simply install them and enable --with-llvm on copperhead, but I then discovered that this caused lots of segmentation faults and I had to revert the --with-llvm again. Sorry about not first testing without submitting results.
> Unfortunately, the log files saved don't include coredump information,
> maybe because of inappropriate core_pattern.
I had increased the core file size limit in /etc/security/limits.conf, but in Trixie this is overruled by a default /etc/security/limits.d/10-coredump-debian.conf. Moreover, the core_pattern was set by apport on the Ubuntu lxc host, but apport is not available in the Trixie lxc guest. I have now corrected both issues, and a simple test resulted in a core file being written to the current directory, like it was before the upgrade.
Best regards,
Tom
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Karlsson | 2024-12-02 15:39:11 | Re: Collation & ctype method table, and extension hooks |
Previous Message | Matthias van de Meent | 2024-12-02 15:08:02 | Re: Incorrect result of bitmap heap scan. |