| From: | "anarazel(at)anarazel(dot)de" <andres(at)anarazel(dot)de> |
|---|---|
| To: | Peter Geoghegan <peter(dot)geoghegan86(at)gmail(dot)com> |
| 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> |
| Subject: | Re: overlapping strncpy/memcpy errors via valgrind |
| Date: | 2013-02-17 19:39:59 |
| Message-ID: | 27655911-2fcf-44b5-85f5-b6b6c0859141@email.android.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Geoghegan <peter(dot)geoghegan86(at)gmail(dot)com> schrieb:
>On 17 February 2013 18:52, anarazel(at)anarazel(dot)de <andres(at)anarazel(dot)de>
>wrote:
>> You already need a suppression file to use valgrind sensibly, its
>easy enough to add it there. Perhaps we should add one to the tree?
>
>Perhaps you should take the time to submit a proper Valgrind patch
>first. The current approach of applying the patch that Noah Misch
>originally wrote (but did not publicly submit, iirc) on an ad-hoc
>basis isn't great. That is what you've done here, right?
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.
Andres
---
Please excuse brevity and formatting - I am writing this on my mobile phone.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2013-02-17 19:52:16 | Re: overlapping strncpy/memcpy errors via valgrind |
| Previous Message | Peter Geoghegan | 2013-02-17 19:31:44 | Re: overlapping strncpy/memcpy errors via valgrind |