On Wed, 16 Jun 2010 22:58:54 -0700, Carl Worth wrote:
> Is valgrind failing to substitute its own strlen implementation for some
> reason? It seems to be, as I'm getting errors from a simple function
> like this:
[snip example with errors from __strlen_sse2]
I switched from the Debian version of
> > http://valgrind.org/docs/manual/dist.readme-packagers.html
> The problem is that strlen() process data 4 bytes by 4 bytes, so it can
> read up to 3 bytes more if the first byte is 0. That's why valgrind
> triggers here.
The page cited above says:
Reason for this is that Valgrind's Memc
reassign 585809 valgrind
thanks
On Mon, Jun 14, 2010 at 11:31:19AM +0200, Aurelien Jarno wrote:
> On Sun, Jun 13, 2010 at 04:48:09PM -0700, Nick Lewycky wrote:
> > Package: valgrind
> > Version: 1:3.5.0-3
> > Severity: important
> >
> > A change in /lib/ld-linux.so.2 has made valgrind report an e
On Sun, Jun 13, 2010 at 04:48:09PM -0700, Nick Lewycky wrote:
> Package: valgrind
> Version: 1:3.5.0-3
> Severity: important
>
> A change in /lib/ld-linux.so.2 has made valgrind report an excess number of
> errors:
>
> $ valgrind /bin/true
> ==6032== Memcheck, a memory error detector
> ==6032== C
Package: valgrind
Version: 1:3.5.0-3
Severity: important
A change in /lib/ld-linux.so.2 has made valgrind report an excess number of
errors:
$ valgrind /bin/true
==6032== Memcheck, a memory error detector
==6032== Copyright (C) 2002-2009, and GNU GPL'd, by Julian Seward et al.
==6032== Using Valg
5 matches
Mail list logo
