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

From: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Daniel Gustafsson <daniel(at)yesql(dot)se>, 13952878799(at)163(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19092: scram_free() will free on address which was not malloc()-ed in pg_scram_mech
Date: 2025-10-23 15:05:14
Message-ID: CAOYmi+=_8KOurhxXiMjd85E7v2ZX+Cj4RpYJzBJAhMz2PDjfRg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Oct 22, 2025 at 5:29 PM Michael Paquier <michael(at)paquier(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Xuneng Zhou 2025-10-24 06:20:39 Re: BUG #19093: Behavioral change in walreceiver termination between PostgreSQL 14.17 and 14.18
Previous Message Amit Langote 2025-10-23 12:07:57 Re: Segfault in RI UPDATE CASCADE on partitioned tables with LIKE+ATTACH child (attnum drift)