Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sHOue-0070XA-Ja for pgsql-bugs@arkaria.postgresql.org; Wed, 12 Jun 2024 14:25:21 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sHOub-000wSv-NQ for pgsql-bugs@arkaria.postgresql.org; Wed, 12 Jun 2024 14:25:18 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sHOKN-000bN4-CL for pgsql-bugs@lists.postgresql.org; Wed, 12 Jun 2024 13:47:52 +0000 Received: from mo4-p00-ob.smtp.rzone.de ([81.169.146.161]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sHOKK-000xlX-G6 for pgsql-bugs@lists.postgresql.org; Wed, 12 Jun 2024 13:47:50 +0000 ARC-Seal: i=1; a=rsa-sha256; t=1718200065; cv=none; d=strato.com; s=strato-dkim-0002; b=nPTowBSIQNLv++daLU1XJgGzm7zvBoB1NXw1DP/ZN8SKO9ixpOK/80lpDJIXibDtsV EJWOuSfO0qb3FRzbfjXgDujBj40ZDk5qmyRLLMXdax7xLhmayAMsI9QU11U3N/j8lYEY /LHUn51vsoZHuxaVYdPSgpTk2qUrTslMfRnP44jpao6r0V46ooGGLGrLH4CgHuhSqo+4 paYCsWs78kI7dpUn0XBCosuo1bc22kyfo3eI7lJPvsZRKQ6QVDKG+hNBQcSWErseid2o UP5+49IQe129jlzNhJFb9hhLEyxlVipbJFDtBbQquVHkxk8DEiFYGEBF508kRVAEAXYv XSmg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; t=1718200065; s=strato-dkim-0002; d=strato.com; h=In-Reply-To:From:References:To:Subject:Date:Message-ID:Cc:Date:From: Subject:Sender; bh=lPtXbhm2AgvnkWO3gVULTSgDfaLvmAWNgahJ8hvCTec=; b=VH6RC54jft5NVyfmuEOUtRkm0QOIWk6n4Pj4JnG9eN37Py0mBDWIJ2Gg5z5kEFeje9 zx9bC1w5S8FT7Nd2bNeJg7KEtoqRd+1AF+Ptues4woDbd+e+T0ieWWgahvxxz/4eL1rY dB0Z9D/BrzJfqgkbxAt1qQa4BROovFlUeiWv8JOif8YoeDZ+gKB/UwBkJvWAHVW0xmU4 m276IhitxLADNZGQTBrVhas8IaJUhT7beM1O76DDnXBsUMSGtvsxLrazo5SkKEYeVsLF bQjDZ2dBDVCLOMkfgOwnwOTQ8hIjqA6KI6wwFOA9RmPbBw6X/uw+asvzkA4M3Q2R1qOB xt1Q== ARC-Authentication-Results: i=1; strato.com; arc=none; dkim=none X-RZG-CLASS-ID: mo00 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1718200065; s=strato-dkim-0002; d=heine7.de; h=In-Reply-To:From:References:To:Subject:Date:Message-ID:Cc:Date:From: Subject:Sender; bh=lPtXbhm2AgvnkWO3gVULTSgDfaLvmAWNgahJ8hvCTec=; b=XKb31yXgVlkI01A7sYLJibvdYJvlYDO+NWirSUx0bGfBIi6kVjvm/kq8nuZhg1oNeW obaG2SMDT6tczGnxOnKD8V3Sp5dY1cMXWoX7eCJ3fbjRLY4xnRHnq9RI3Sfi7yYeoKbi JgBVTIb0ItIdXWQc6axF2FyHwi859pzDrZrpcg2ot8g8KpmcFMSB8Hv2Sa8kIlhb3ofh Q7gYdpINSuoGmr/+QgbcHOtD2mXXaE6ccoJPH96doSumyTLxIE0j92pui/sHPd78e7sf nEXoi2nTs4gKF/3Cnx7uUwsX57j97YaYJ3eXKYvv8NdkH3QSbAXvplmpxMDhz3UvHicF aS6Q== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; t=1718200065; s=strato-dkim-0003; d=heine7.de; h=In-Reply-To:From:References:To:Subject:Date:Message-ID:Cc:Date:From: Subject:Sender; bh=lPtXbhm2AgvnkWO3gVULTSgDfaLvmAWNgahJ8hvCTec=; b=UUBCCaRzYyzEFwNMEyD1vgR8GX2lOM+oFBcInldXlYaCETdLEyFiaIF61IXVB9RAiu o6Fbc5D864YdwMX+6HBw== X-RZG-AUTH: ":K2UQfVWqNexjutYFLWF4K6qbrznTNjZhogOPhnqUGmgNZnxZB9kOFZ0wXqH/Zmz0Mm6b7MShLk1BKg==" Received: from [192.168.6.17] by smtp.strato.de (RZmta 50.5.0 DYNA|AUTH) with ESMTPSA id Y05c3e05CDli5Xu (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits)) (Client did not present a certificate); Wed, 12 Jun 2024 15:47:44 +0200 (CEST) Content-Type: multipart/alternative; boundary="------------PLTEl3vEoJjeay0D6n6GFS0m" Message-ID: Date: Wed, 12 Jun 2024 15:47:44 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: BUG #18503: Reproducible 'Segmentation fault' in 16.3 on ARM64 To: Thomas Munro , pgsql-bugs@lists.postgresql.org References: <18503-6e0f5ab2f9c319c1@postgresql.org> Content-Language: en-US, de-DE From: Stefan Heine In-Reply-To: Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------PLTEl3vEoJjeay0D6n6GFS0m Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 2024-06-12 02:59, Thomas Munro wrote: > On Tue, Jun 11, 2024 at 10:08 PM PG Bug reporting form > 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? --------------PLTEl3vEoJjeay0D6n6GFS0m Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit

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?

--------------PLTEl3vEoJjeay0D6n6GFS0m--