Re: Using Valgrind to detect faulty buffer accesses (no pin or buffer content lock held)

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Masahiko Sawada <masahiko(dot)sawada(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Using Valgrind to detect faulty buffer accesses (no pin or buffer content lock held)
Date: 2020-07-02 17:11:53
Message-ID: CAH2-WzkQhGE4Z5U-W-cXpYQTsp7C7_mt8y+y1zj-n9nqyo6+rQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jul 2, 2020 at 7:48 AM Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
> This patch fails to apply to HEAD due to conflicts in nbtpage.c, can you please
> submit a rebased version?

I attach the rebased patch series.

Thanks
--
Peter Geoghegan

Attachment Content-Type Size
v3-0002-Add-nbtree-Valgrind-buffer-lock-checks.patch application/octet-stream 14.6 KB
v3-0001-Add-Valgrind-buffer-access-instrumentation.patch application/octet-stream 2.3 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jaka Jančar 2020-07-02 17:18:25 Re: Sync vs Flush
Previous Message Pavel Stehule 2020-07-02 17:09:57 Re: proposal: unescape_text function