Snapshots for CURRENT

[Russ Allbery]

Julien ÉLIE <julien at trigofacile.com> writes:

> But if that is the case, it would have already failed with the first
> test (authprogs/ckpasswd.t) since a similar uninitialised value appears:

> %valgrind ./ckpasswd.t
> ==9349==
> ==9349== Conditional jump or move depends on uninitialised value(s)
> ==9349==    at 0x4008ED5: (within /lib/ld-2.3.6.so)

This stuff you can ignore.  It's noise from glibc, which valgrind doesn't
understand.  You have to look for valgrind messages entirely from our
code.

> By the way, I have for innd/artparse.t:

> ==9259== Invalid write of size 1
> ==9259==    at 0x805257F: ARTsetup (art.c:287)
> ==9259==    by 0x8051628: initialize (artparse-t.c:98)
> ==9259==    by 0x8051A19: main (artparse-t.c:175)
> ==9259==  Address 0x42DF927 is 1 bytes before a block of size 1 alloc'd
> ==9259==    at 0x401D38B: malloc (vg_replace_malloc.c:149)
> ==9259==    by 0x80A296A: x_strdup (xmalloc.c:128)
> ==9259==    by 0x8052569: ARTsetup (art.c:286)
> ==9259==    by 0x8051628: initialize (artparse-t.c:98)
> ==9259==    by 0x8051A19: main (artparse-t.c:175)

I haven't looked at that in detail yet, but that definitely looks like a
bug.

-- 
Russ Allbery (rra at stanford.edu)             <http://www.eyrie.org/~eagle/>

    Please send questions to the list rather than mailing me directly.
     <http://www.eyrie.org/~eagle/faqs/questions.html> explains why.