Re: overlapping strncpy/memcpy errors via valgrind - Mailing list pgsql-hackers

From anarazel@anarazel.de
Subject Re: overlapping strncpy/memcpy errors via valgrind
Date
Msg-id 27655911-2fcf-44b5-85f5-b6b6c0859141@email.android.com
Whole thread Raw
In response to Re: overlapping strncpy/memcpy errors via valgrind  (Peter Geoghegan <peter.geoghegan86@gmail.com>)
Responses Re: overlapping strncpy/memcpy errors via valgrind
List pgsql-hackers

Peter Geoghegan <peter.geoghegan86@gmail.com> schrieb:

>On 17 February 2013 18:52, anarazel@anarazel.de <andres@anarazel.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
applyto make pg inside valgrind work on amd64. 

Andres

---
Please excuse brevity and formatting - I am writing this on my mobile phone.



pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: overlapping strncpy/memcpy errors via valgrind
Next
From: Peter Geoghegan
Date:
Subject: Re: overlapping strncpy/memcpy errors via valgrind