|
From: Tom H. <th...@cy...> - 2004-02-28 17:22:54
|
In message <E1A...@du...>
Tom Hughes <to...@co...> wrote:
> == 126 tests, 15 stderr failures, 1 stdout failure =================
> corecheck/tests/fdleak_cmsg (stderr)
> corecheck/tests/fdleak_creat (stderr)
> corecheck/tests/fdleak_dup (stderr)
> corecheck/tests/fdleak_dup2 (stderr)
> corecheck/tests/fdleak_fcntl (stderr)
> corecheck/tests/fdleak_ipv4 (stderr)
> corecheck/tests/fdleak_open (stderr)
> corecheck/tests/fdleak_pipe (stderr)
> corecheck/tests/fdleak_socketpair (stderr)
> helgrind/tests/inherit (stderr)
> memcheck/tests/buflen_check (stderr)
> memcheck/tests/execve (stderr)
> memcheck/tests/fwrite (stderr)
> memcheck/tests/weirdioctl (stderr)
> memcheck/tests/writev (stderr)
> none/tests/exec-sigmask (stdout)
Most of these are failures of this form (the exact system call varies):
***************
*** 5 ****
! at 0x........: accept (in /...libc...)
--- 5 ----
! at 0x........: _dl_sysinfo_int80 (in /lib/ld-2.3.2.so)
This is down to the FC1 kernel/glibc combination making use of the sysinfo
page so that all system calls appear to occur in _dl_sysinfo_int80 but I did
think that Jeremy had put a hack in valgrind to make it back out to the next
function in that case when printing the stack trace.
The helgrind inherit test is as discussed in the RH 8 analysis and the
only other failure is none/tests/exec-sigmask which is reporting this:
***************
*** 0 ****
--- 1 ----
+ signal 32 missing from mask
I suspect something in glibc is removing signal 32 from the mask during
the exec or something, given that glibc uses that signal itself.
Tom
--
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/
|