Re: [BUG] PostgreSQL crashes with ThreadSanitizer during early initialization

From: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Emmanuel Sibi <emmanuelsibi(dot)mec(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Andres Freund <andres(at)anarazel(dot)de>
Subject: Re: [BUG] PostgreSQL crashes with ThreadSanitizer during early initialization
Date: 2025-11-05 00:14:52
Message-ID: CAOYmi+kW2qS1jEGTa2Ev7tSqrrB3M7SCikN6FrjTSYwQVcdEeQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Nov 4, 2025 at 2:39 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Another problem is that it only defends against a limited set of
> sanitizers, though presumably every single one is broken in the same
> way (compare [1]).

How about __attribute__((disable_sanitizer_instrumentation)) ? LLVM's
own tests make some use of this [1].

--Jacob

[1] https://github.com/llvm/llvm-project/blob/2b4ac6629/compiler-rt/test/sanitizer_common/TestCases/dlsym_alloc.c

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2025-11-05 00:16:58 Re: Have the planner convert COUNT(1) / COUNT(not_null_col) to COUNT(*)
Previous Message Masahiko Sawada 2025-11-04 23:50:11 Re: Add CHECK_FOR_INTERRUPTS in Evict{Rel,All}UnpinnedBuffers