From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jehan-Guillaume de Rorthais <jgdr@dalibo.com>
Cc: pgsql-hackers@lists.postgresql.org
Subject: Re: segmentation fault when cassert enabled
Date: Fri, 25 Oct 2019 12:28:38 -0400
Message-ID: <18714.1572020918@sss.pgh.pa.us> (raw)
In-Reply-To: <20191025175929.7e90dbf5@firost>
References: <20191025175929.7e90dbf5@firost>
Jehan-Guillaume de Rorthais <jgdr@dalibo.com> writes:
> When investigating for the bug reported in thread "logical replication -
> negative bitmapset member not allowed", I found a way to seg fault postgresql
> only when cassert is enabled.
> ...
> I hadn't time to digg further yet. However, I don't understand why this crash
> is triggered when cassert is enabled.
Most likely, it's not so much assertions that provoke the crash as
CLOBBER_FREED_MEMORY, ie the actual problem here is use of already-freed
memory.
regards, tom lane
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-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, jgdr@dalibo.com, pgsql-hackers@lists.postgresql.org
Subject: Re: segmentation fault when cassert enabled
In-Reply-To: <18714.1572020918@sss.pgh.pa.us>
* 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