Re: LLVM Address Sanitizer (ASAN) and valgrind support

From: Greg Stark <stark(at)mit(dot)edu>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: LLVM Address Sanitizer (ASAN) and valgrind support
Date: 2016-09-27 23:23:11
Message-ID: CAM-w4HOm_JAi7XcpFvw_kpz1PXxDiS2y4sOTq0uwTX1-zEz+RQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Sep 27, 2016 at 11:02 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> Any plans to pick this up again?

Yeah, I was just thinking I should pick this up again.

> I vote for renaming the VALGRIND names etc. to something more tool-neutral. I think it's going to be too confusing otherwise.

Hm, the danger there is once I start refactoring things I could get
bogged down... I would love to remove all the #ifdef's and have the
macros just be no-ops if they're compiled out for example...

--
greg

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2016-09-27 23:24:49 hash_create(nelem = 0) does invalid memory accesses
Previous Message Vitaly Burovoy 2016-09-27 22:57:44 Re: Detect supported SET parameters when pg_restore is run