Re: BUG #19092: scram_free() will free on address which was not malloc()-ed in pg_scram_mech - Mailing list pgsql-bugs

From Jacob Champion
Subject Re: BUG #19092: scram_free() will free on address which was not malloc()-ed in pg_scram_mech
Date
Msg-id CAOYmi+=_8KOurhxXiMjd85E7v2ZX+Cj4RpYJzBJAhMz2PDjfRg@mail.gmail.com
Whole thread Raw
In response to Re: BUG #19092: scram_free() will free on address which was not malloc()-ed in pg_scram_mech  (Michael Paquier <michael@paquier.xyz>)
List pgsql-bugs
On Wed, Oct 22, 2025 at 5:29 PM Michael Paquier <michael@paquier.xyz> wrote:
> > So: test case, please.
>
> Yes.

Thirded.

The only thing I can think of at the moment -- which a test case would
quickly prove or disprove -- is that the symbol visibility is messed
up for this particular build in some way, and libpq's pg_saslprep has
been incorrectly preempted by postgres' pg_saslprep. But I can't
reproduce anything like that with my local macOS build.

--Jacob



pgsql-bugs by date:

Previous
From: Amit Langote
Date:
Subject: Re: Segfault in RI UPDATE CASCADE on partitioned tables with LIKE+ATTACH child (attnum drift)
Next
From: Xuneng Zhou
Date:
Subject: Re: BUG #19093: Behavioral change in walreceiver termination between PostgreSQL 14.17 and 14.18