|
From: Tom H. <th...@cy...> - 2004-02-28 18:16:03
|
In message <E1A...@st...>
Tom Hughes <th...@cy...> wrote:
> Last 20 lines of log.verbose follow
>
> memcheck/tests/pushfpopf (stderr)
> memcheck/tests/realloc1 (stderr)
> memcheck/tests/realloc2 (stderr)
> memcheck/tests/realloc3 (stderr)
> memcheck/tests/sigaltstack (stderr)
> memcheck/tests/signal2 (stderr)
> memcheck/tests/supp1 (stderr)
> memcheck/tests/supp2 (stderr)
> memcheck/tests/suppfree (stderr)
> memcheck/tests/threadederrno (stderr)
> memcheck/tests/trivialleak (stderr)
> memcheck/tests/tronical (stderr)
> memcheck/tests/weirdioctl (stderr)
> memcheck/tests/writev (stderr)
> memcheck/tests/zeropage (stderr)
> none/tests/pth_blockedsig (stdout)
> none/tests/pth_blockedsig (stderr)
> none/tests/yield (stdout)
> none/tests/yield (stderr)
There are a number of failures here of this form:
***************
*** 2 ****
--- 3,7 ----
+ valgrind's libpthread.so: init_libc_tsd_keys: lock
+ Please report this bug at: valgrind.kde.org
Which is a bit odd, because from looking at the code it means that
the attempt to lock the mutex in init_libc_tsd_keys is failing for
some reason.
There are also a number that look something like this:
***************
*** 5 ****
! at 0x........: fcntl (in /...libc...)
--- 5 ----
! at 0x........: fcntl (../sysdeps/unix/sysv/linux/i386/fcntl.c:49)
Which are presumably caused by the C library having debugging symbols
in it for some reason.
Some are caused by a couple of rules being commented out in glibc-2.2.supp
for some reason - possibly due to a typo in the rules. A patch for that is
attached - it also adds a couple of new suppressions that are needed.
There is also a new assertion firing in some tests:
+ valgrind: vg_libpthread.c:... (pthread_cond_init): Assertion `sizeof(*cond) >=
sizeof(vg_pthread_cond_t)' failed.
Presumably pthread_cond_t is a bit smaller in glibc 2.2 or something.
Tom
--
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/
|