On Mon, 30 May 2011 09:15:47 -0000, Alexey Kopytov <email address hidden> wrote:
> It turns out the bug is not repeatable on a valgrind-enabled build.
> Going to revert my fix and close the bug as invalid. Will reopen if the
> bug proves to be repeatable with a valgrind build.
It's been a while for me, but I wonder what the different options are
for valgrind build? Maybe there is code in there to zero out the row
buffer (but built only for valgrind builds)?
On Mon, 30 May 2011 09:15:47 -0000, Alexey Kopytov <email address hidden> wrote:
> It turns out the bug is not repeatable on a valgrind-enabled build.
> Going to revert my fix and close the bug as invalid. Will reopen if the
> bug proves to be repeatable with a valgrind build.
It's been a while for me, but I wonder what the different options are
for valgrind build? Maybe there is code in there to zero out the row
buffer (but built only for valgrind builds)?
--
Stewart Smith