| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Greg Stark <stark(at)mit(dot)edu> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: LLVM Address Sanitizer (ASAN) and valgrind support |
| Date: | 2016-09-27 22:02:27 |
| Message-ID: | 20160927220227.m5hrj54tqhkaqasw@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2015-09-07 17:05:10 +0100, Greg Stark wrote:
> I feel like I remember hearing about this before but I can't find any
> mention of it in my mail archives. It seems pretty simple to add
> support for LLVM's Address Sanitizer (asan) by using the hooks we
> already have for valgrind.
Any plans to pick this up again?
> In fact I think this would actually be sufficient. I'm not sure what
> the MEMPOOL valgrind stuff is though. I don't think it's relevant to
> address sanitizer which only tracks references to free'd or
> unallocated pointers.
It'd be nice to add msan support, so uninitialized accesses are also
tracked. (oh, you suggest that below)
I vote for renaming the VALGRIND names etc. to something more
tool-neutral. I think it's going to be too confusing otherwise.
Andres
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-09-27 22:48:19 | Re: Re: [GENERAL] inconsistent behaviour of set-returning functions in sub-query with random() |
| Previous Message | Vitaly Burovoy | 2016-09-27 21:52:24 | Re: Detect supported SET parameters when pg_restore is run |