On 09/08/2016 01:56 PM, Mark Wielaard wrote:
On Wed, Sep 07, 2016 at 04:21:29PM -0700, Paul Eggert wrote:
On 09/07/2016 04:52 AM, Mark Wielaard wrote:
If valgrind believes the
memory isn't in valid memory then it will complain about an invalid access.
But if the memory is accessible but uninitialised then it will just track
the undefinedness complain later if such a value is used.
I think the former is what happened in Gnulib fts.c before Gnulib was fixed.
BTW. Do gnulib and glibc syncronize? I had no idea gnulib also contained
fts. I recently fixed some issue (adding LFS support) in glibc.
They are expected to synchronize. It does not always happen.
Florian
