| From: | Peter Geoghegan <peter(dot)geoghegan86(at)gmail(dot)com> |
|---|---|
| To: | "anarazel(at)anarazel(dot)de" <andres(at)anarazel(dot)de> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Boszormenyi Zoltan <zb(at)cybertec(dot)at>, Andres Freund <andres(at)2ndquadrant(dot)com>, Greg Stark <stark(at)mit(dot)edu>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Noah Misch <noah(at)leadboat(dot)com> |
| Subject: | Re: overlapping strncpy/memcpy errors via valgrind |
| Date: | 2013-02-17 19:52:16 |
| Message-ID: | CAEYLb_XnbSF6GBVv0OoQdYMGgtqd-Rdpa+ByvctE2dJsin1cjw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 17 February 2013 19:39, anarazel(at)anarazel(dot)de <andres(at)anarazel(dot)de> wrote:
> What patch are you talking about? I have no knowledge about any pending valgrind patches except one I made upstream apply to make pg inside valgrind work on amd64.
Noah wrote a small patch, which he shared with me privately, which
added Valgrind hook macros to aset.c and mcxt.c. The resulting
Valgrind run threw up some things that were reported publicly [1]. I
documented much of his work on the wiki. I was under the impression
that this was the best way to get Valgrind to work with Postgres
(apparently there were problems with many false positives otherwise).
[1] http://www.postgresql.org/message-id/20110312133224.GA7833@tornado.gateway.2wire.net
--
Regards,
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2013-02-17 20:19:54 | Re: PATCH: Split stats file per database WAS: autovacuum stress-testing our system |
| Previous Message | anarazel@anarazel.de | 2013-02-17 19:39:59 | Re: overlapping strncpy/memcpy errors via valgrind |