From: Stefan Heine <github.stheine@heine7.de>
To: Thomas Munro <thomas.munro@gmail.com>
To: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18503: Reproducible 'Segmentation fault' in 16.3 on ARM64
Date: Wed, 12 Jun 2024 15:47:44 +0200
Message-ID: <e35fafdb-9b2c-4259-aae5-0e8312a2a8f6@heine7.de> (raw)
In-Reply-To: <CA+hUKGJNtO=wZ2X1nDpFDrF_J7Xo7LnFinaTh-qT2vmqoHSJKQ@mail.gmail.com>
References: <18503-6e0f5ab2f9c319c1@postgresql.org>
<CA+hUKGJNtO=wZ2X1nDpFDrF_J7Xo7LnFinaTh-qT2vmqoHSJKQ@mail.gmail.com>
On 2024-06-12 02:59, Thomas Munro wrote:
> On Tue, Jun 11, 2024 at 10:08 PM PG Bug reporting form
> <noreply@postgresql.org> wrote:
>> The query described in
>> https://www.postgresql.org/message-id/flat/18471-4e01d7601cedf1b0%40postgresql.org
>> is causing a reproducible 'Segmentation fault'.
> Also on ARM?
yes, this is ARM (aarch64).
> That other report said that memory is leaking and implies (?) the OOM
> killer, but you're talking about a segmentation fault, so it seems
> like a different symptom (even if the root cause is same), right?
when jit is disabled, the query runs ok in < 2 seconds.
when the issue happens, it takes > 30 seconds and then results in a 6GB
core.
>> That situation is clearly reproducible, so we can help troubleshooting in
>> case you want to look into details.
> Can you get a core file, and gdb backtrace?
find a core here:
https://my.hidrive.com/share/bz2zb2alkp
do you have instructions for the gdb backtrace?
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: github.stheine@heine7.de, thomas.munro@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18503: Reproducible 'Segmentation fault' in 16.3 on ARM64
In-Reply-To: <e35fafdb-9b2c-4259-aae5-0e8312a2a8f6@heine7.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox