You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
(122) |
Nov
(152) |
Dec
(69) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(6) |
Feb
(25) |
Mar
(73) |
Apr
(82) |
May
(24) |
Jun
(25) |
Jul
(10) |
Aug
(11) |
Sep
(10) |
Oct
(54) |
Nov
(203) |
Dec
(182) |
| 2004 |
Jan
(307) |
Feb
(305) |
Mar
(430) |
Apr
(312) |
May
(187) |
Jun
(342) |
Jul
(487) |
Aug
(637) |
Sep
(336) |
Oct
(373) |
Nov
(441) |
Dec
(210) |
| 2005 |
Jan
(385) |
Feb
(480) |
Mar
(636) |
Apr
(544) |
May
(679) |
Jun
(625) |
Jul
(810) |
Aug
(838) |
Sep
(634) |
Oct
(521) |
Nov
(965) |
Dec
(543) |
| 2006 |
Jan
(494) |
Feb
(431) |
Mar
(546) |
Apr
(411) |
May
(406) |
Jun
(322) |
Jul
(256) |
Aug
(401) |
Sep
(345) |
Oct
(542) |
Nov
(308) |
Dec
(481) |
| 2007 |
Jan
(427) |
Feb
(326) |
Mar
(367) |
Apr
(255) |
May
(244) |
Jun
(204) |
Jul
(223) |
Aug
(231) |
Sep
(354) |
Oct
(374) |
Nov
(497) |
Dec
(362) |
| 2008 |
Jan
(322) |
Feb
(482) |
Mar
(658) |
Apr
(422) |
May
(476) |
Jun
(396) |
Jul
(455) |
Aug
(267) |
Sep
(280) |
Oct
(253) |
Nov
(232) |
Dec
(304) |
| 2009 |
Jan
(486) |
Feb
(470) |
Mar
(458) |
Apr
(423) |
May
(696) |
Jun
(461) |
Jul
(551) |
Aug
(575) |
Sep
(134) |
Oct
(110) |
Nov
(157) |
Dec
(102) |
| 2010 |
Jan
(226) |
Feb
(86) |
Mar
(147) |
Apr
(117) |
May
(107) |
Jun
(203) |
Jul
(193) |
Aug
(238) |
Sep
(300) |
Oct
(246) |
Nov
(23) |
Dec
(75) |
| 2011 |
Jan
(133) |
Feb
(195) |
Mar
(315) |
Apr
(200) |
May
(267) |
Jun
(293) |
Jul
(353) |
Aug
(237) |
Sep
(278) |
Oct
(611) |
Nov
(274) |
Dec
(260) |
| 2012 |
Jan
(303) |
Feb
(391) |
Mar
(417) |
Apr
(441) |
May
(488) |
Jun
(655) |
Jul
(590) |
Aug
(610) |
Sep
(526) |
Oct
(478) |
Nov
(359) |
Dec
(372) |
| 2013 |
Jan
(467) |
Feb
(226) |
Mar
(391) |
Apr
(281) |
May
(299) |
Jun
(252) |
Jul
(311) |
Aug
(352) |
Sep
(481) |
Oct
(571) |
Nov
(222) |
Dec
(231) |
| 2014 |
Jan
(185) |
Feb
(329) |
Mar
(245) |
Apr
(238) |
May
(281) |
Jun
(399) |
Jul
(382) |
Aug
(500) |
Sep
(579) |
Oct
(435) |
Nov
(487) |
Dec
(256) |
| 2015 |
Jan
(338) |
Feb
(357) |
Mar
(330) |
Apr
(294) |
May
(191) |
Jun
(108) |
Jul
(142) |
Aug
(261) |
Sep
(190) |
Oct
(54) |
Nov
(83) |
Dec
(22) |
| 2016 |
Jan
(49) |
Feb
(89) |
Mar
(33) |
Apr
(50) |
May
(27) |
Jun
(34) |
Jul
(53) |
Aug
(53) |
Sep
(98) |
Oct
(206) |
Nov
(93) |
Dec
(53) |
| 2017 |
Jan
(65) |
Feb
(82) |
Mar
(102) |
Apr
(86) |
May
(187) |
Jun
(67) |
Jul
(23) |
Aug
(93) |
Sep
(65) |
Oct
(45) |
Nov
(35) |
Dec
(17) |
| 2018 |
Jan
(26) |
Feb
(35) |
Mar
(38) |
Apr
(32) |
May
(8) |
Jun
(43) |
Jul
(27) |
Aug
(30) |
Sep
(43) |
Oct
(42) |
Nov
(38) |
Dec
(67) |
| 2019 |
Jan
(32) |
Feb
(37) |
Mar
(53) |
Apr
(64) |
May
(49) |
Jun
(18) |
Jul
(14) |
Aug
(53) |
Sep
(25) |
Oct
(30) |
Nov
(49) |
Dec
(31) |
| 2020 |
Jan
(87) |
Feb
(45) |
Mar
(37) |
Apr
(51) |
May
(99) |
Jun
(36) |
Jul
(11) |
Aug
(14) |
Sep
(20) |
Oct
(24) |
Nov
(40) |
Dec
(23) |
| 2021 |
Jan
(14) |
Feb
(53) |
Mar
(85) |
Apr
(15) |
May
(19) |
Jun
(3) |
Jul
(14) |
Aug
(1) |
Sep
(57) |
Oct
(73) |
Nov
(56) |
Dec
(22) |
| 2022 |
Jan
(3) |
Feb
(22) |
Mar
(6) |
Apr
(55) |
May
(46) |
Jun
(39) |
Jul
(15) |
Aug
(9) |
Sep
(11) |
Oct
(34) |
Nov
(20) |
Dec
(36) |
| 2023 |
Jan
(79) |
Feb
(41) |
Mar
(99) |
Apr
(169) |
May
(48) |
Jun
(16) |
Jul
(16) |
Aug
(57) |
Sep
(19) |
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
1
(10) |
2
(22) |
3
(15) |
4
(14) |
5
(8) |
6
(10) |
7
(14) |
|
8
(9) |
9
(10) |
10
(21) |
11
(16) |
12
(17) |
13
(15) |
14
(8) |
|
15
(12) |
16
(8) |
17
(44) |
18
(24) |
19
(29) |
20
(29) |
21
(17) |
|
22
(17) |
23
(16) |
24
(18) |
25
(16) |
26
(15) |
27
(16) |
28
(11) |
|
29
(11) |
30
(10) |
31
(12) |
|
|
|
|
|
From: Julian S. <js...@ac...> - 2006-01-06 21:43:14
|
> I'm new to the valgrind community. I recently did a complete build of > valgrid-3.1.0 release on a Power5 machine. After doing make regtest I > found total of 21 tests failure. These may be known or not, but I just > wanted to report them to the mailing list anyway. Thanks. Most of these are harmless - they happen on a PPC970 box too. We should improve our regression test mechanism so it only reports a failure when there really is one, but that's not as simple as it sounds. > none/tests/ppc32/jm-vmx (stdout) > none/tests/ppc32/jm-vmx (stderr) > none/tests/ppc32/testVMX (stdout) > none/tests/ppc32/testVMX (stderr) These are VMX (Altivec) tests. I presume they failed because POWER5 doesn't support Altivec (right?) > none/tests/ppc32/jm-insns (stdout) > none/tests/ppc32/jm-insns (stderr) These should not fail -- tests of the basic integer instruction set. Can you send none/tests/ppc32/jm-insns.stdout.diff and none/tests/ppc32/jm-insns.stderr.diff so we can see why they failed. J |
|
From: Uttam P. <ut...@us...> - 2006-01-06 19:39:26
|
Hi, I'm new to the valgrind community. I recently did a complete build of valgrid-3.1.0 release on a Power5 machine. After doing make regtest I found total of 21 tests failure. These may be known or not, but I just wanted to report them to the mailing list anyway. Following is the result, == 174 tests, 18 stderr failures, 3 stdout failures ================= memcheck/tests/badjump (stderr) memcheck/tests/badjump2 (stderr) memcheck/tests/leak-cycle (stderr) memcheck/tests/leak-tree (stderr) memcheck/tests/mempool (stderr) memcheck/tests/partiallydefinedeq (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/supp1 (stderr) memcheck/tests/supp_unknown (stderr) memcheck/tests/toobig-allocs (stderr) memcheck/tests/xml1 (stderr) massif/tests/toobig-allocs (stderr) none/tests/faultstatus (stderr) none/tests/fdleak_cmsg (stderr) none/tests/mremap (stderr) none/tests/ppc32/jm-insns (stdout) none/tests/ppc32/jm-insns (stderr) none/tests/ppc32/jm-vmx (stdout) none/tests/ppc32/jm-vmx (stderr) none/tests/ppc32/testVMX (stdout) none/tests/ppc32/testVMX (stderr) make: *** [regtest] Error 1 Enviornment: Hardware: Power5 (with 8 8 processors) OS: Linux elm3b149 2.6.5-7.97-pseries64.nm #1 SMP Thu Mar 31 10:55:11 PST 2005 ppc64 ppc64 ppc64 GNU/Linux gcc -v: Reading specs from /usr/lib/gcc-lib/powerpc-suse-linux/3.3.3/specs Configured with: ../configure --enable-threads=posix --prefix=/usr --with-local-prefix=/usr/local --infodir=/usr/share/info --mandir=/usr/share/man --enable-languages=c,c++,f77,objc,java,ada --disable-checking --libdir=/usr/lib --enable-libgcj --with-gxx-include-dir=/usr/include/g++ --with-slibdir=/lib --with-system-zlib --enable-shared --enable-__cxa_atexit --host=powerpc-suse-linux --build=powerpc-suse-linux --target=powerpc-suse-linux --enable-targets=powerpc64-suse-linux --enable-biarch Thread model: posix gcc version 3.3.3 (SuSE Linux) Please let me know if I'm missing some piece of information to mention in this email. Also, let me know (which somebody will) if this is not the right forum for this kind of information/questions. Thanks, Uttam |
|
From: Ashley P. <as...@qu...> - 2006-01-06 15:42:14
|
On Sat, 2005-12-24 at 12:15 -0600, Nicholas Nethercote wrote: > Hi, > > In the recent Valgrind survey five people complained about the difficulty > of tracking down the root cause of undefined value errors, caused by the > fact that Memcheck waits until an undefined value can affect the visible > behaviour of the program (eg. is used in a conditional branch, or a > syscall input). I've often wondered why Valgrind didn't check at this level, it's what I always thought it should do although I've now come around to the "only report when it has a consequence" model. > I did some experimentation with eager checking a couple of years ago and > found that it caused large numbers of false positives. I repeated the > experiment again yesterday and saw the same results. I changed Memcheck > to complain about the loading of any undefined values and tried various > programs. For the empty C program that just returns zero, I get 24 errors > from 23 contexts, most just from the dynamic linker. I get the following > counts for the following programs: > > empty 1 errors from 1 context > perf/bz2 8405487 errors from 30 contexts > perf/tinycc 4647525 errors from 301 contexts > I had to use --error-limit=no for these otherwise Memcheck would have > stopped reporting errors after 100,000. These programs have no > (unsuppressed) errors when run with a normal Memcheck. Well that's not overly encouraging but the only numbers that actually matter here are the number of contexts, not the number of errors. > I've attached the output from that last tinycc run. What do you get it you use --num-callers=4?. Does this affect how unique contexts are collated or just how they are displayed. It looks to me like you would only need a small number of suppressions to reduce this error count to almost zero. > It has been suggested that an option be present to do this eager checking, > but I'm not convinced it would be useful given the overwhelming number of > false positives. I'm wondering what other people think. I'd like to see it as an option, huge numbers of false positives can be daunting when you first see them but that's in itself is not a good reason for not having this option. One problem of the current scheme is it can be difficult to find the underlying cause of a undefined value, I'd have thought having this as an option would allow people to pinpoint errors reported by the current scheme much quicker and I'd like to see it for that reason alone. Ashley, |
|
From: <js...@ac...> - 2006-01-06 03:59:13
|
Nightly build on phoenix ( SuSE 10.0 ) started at 2006-01-06 03:30:02 GMT Checking out vex source tree ... done Building vex ... done Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 209 tests, 5 stderr failures, 1 stdout failure ================= memcheck/tests/leak-tree (stderr) memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) none/tests/mremap2 (stdout) none/tests/x86/faultstatus (stderr) none/tests/x86/int (stderr) |
|
From: <js...@ac...> - 2006-01-06 03:49:57
|
Nightly build on g5 ( YDL 4.0, ppc970 ) started at 2006-01-06 04:40:00 CET Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Last 20 lines of verbose log follow echo make[4]: Leaving directory `/home/sewardj/Nightly/valgrind/none/tests/ppc32' Making check in ppc64 make[4]: Entering directory `/home/sewardj/Nightly/valgrind/none/tests/ppc64' make jm-insns make[5]: Entering directory `/home/sewardj/Nightly/valgrind/none/tests/ppc64' if gcc -DHAVE_CONFIG_H -I. -I. -I../../.. -Winline -Wall -O -mregnames -DHAS_ALTIVEC -maltivec -m64 -Wno-long-long -MT jm_insns-jm-insns.o -MD -MP -MF ".deps/jm_insns-jm-insns.Tpo" -c -o jm_insns-jm-insns.o `test -f 'jm-insns.c' || echo './'`jm-insns.c; \ then mv -f ".deps/jm_insns-jm-insns.Tpo" ".deps/jm_insns-jm-insns.Po"; else rm -f ".deps/jm_insns-jm-insns.Tpo"; exit 1; fi jm-insns.c:1: error: syntax error before '.' token jm-insns.c:1:25: warning: no newline at end of file make[5]: *** [jm_insns-jm-insns.o] Error 1 make[5]: Leaving directory `/home/sewardj/Nightly/valgrind/none/tests/ppc64' make[4]: *** [check-am] Error 2 make[4]: Leaving directory `/home/sewardj/Nightly/valgrind/none/tests/ppc64' make[3]: *** [check-recursive] Error 1 make[3]: Leaving directory `/home/sewardj/Nightly/valgrind/none/tests' make[2]: *** [check-recursive] Error 1 make[2]: Leaving directory `/home/sewardj/Nightly/valgrind/none' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/home/sewardj/Nightly/valgrind' make: *** [check] Error 2 |
|
From: Tom H. <to...@co...> - 2006-01-06 03:43:15
|
Nightly build on dunsmere ( athlon, Fedora Core 4 ) started at 2006-01-06 03:30:05 GMT Results differ from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 211 tests, 6 stderr failures, 2 stdout failures ================= memcheck/tests/leak-tree (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/sse1_memory (stdout) none/tests/mremap2 (stdout) none/tests/x86/faultstatus (stderr) none/tests/x86/int (stderr) ================================================= == Results from 24 hours ago == ================================================= Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 211 tests, 7 stderr failures, 2 stdout failures ================= memcheck/tests/leak-tree (stderr) memcheck/tests/mempool (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/sse1_memory (stdout) none/tests/mremap2 (stdout) none/tests/x86/faultstatus (stderr) none/tests/x86/int (stderr) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Fri Jan 6 03:36:35 2006 --- new.short Fri Jan 6 03:42:59 2006 *************** *** 8,12 **** ! == 211 tests, 7 stderr failures, 2 stdout failures ================= memcheck/tests/leak-tree (stderr) - memcheck/tests/mempool (stderr) memcheck/tests/pointer-trace (stderr) --- 8,11 ---- ! == 211 tests, 6 stderr failures, 2 stdout failures ================= memcheck/tests/leak-tree (stderr) memcheck/tests/pointer-trace (stderr) |
|
From: Tom H. <th...@cy...> - 2006-01-06 03:22:44
|
Nightly build on dellow ( x86_64, Fedora Core 4 ) started at 2006-01-06 03:10:09 GMT Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 230 tests, 6 stderr failures, 3 stdout failures ================= memcheck/tests/leakotron (stdout) memcheck/tests/oset_test (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/sse1_memory (stdout) none/tests/amd64/faultstatus (stderr) none/tests/mremap2 (stdout) none/tests/x86/faultstatus (stderr) none/tests/x86/int (stderr) |
|
From: Tom H. <th...@cy...> - 2006-01-06 03:18:53
|
Nightly build on aston ( x86_64, Fedora Core 3 ) started at 2006-01-06 03:05:08 GMT Results differ from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 230 tests, 7 stderr failures, 2 stdout failures ================= memcheck/tests/oset_test (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/scalar_supp (stderr) memcheck/tests/x86/sse1_memory (stdout) none/tests/amd64/faultstatus (stderr) none/tests/mremap2 (stdout) none/tests/x86/faultstatus (stderr) none/tests/x86/int (stderr) ================================================= == Results from 24 hours ago == ================================================= Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 230 tests, 6 stderr failures, 2 stdout failures ================= memcheck/tests/oset_test (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/scalar_supp (stderr) memcheck/tests/x86/sse1_memory (stdout) none/tests/amd64/faultstatus (stderr) none/tests/mremap2 (stdout) none/tests/x86/faultstatus (stderr) none/tests/x86/int (stderr) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Fri Jan 6 03:12:22 2006 --- new.short Fri Jan 6 03:18:49 2006 *************** *** 8,11 **** ! == 230 tests, 6 stderr failures, 2 stdout failures ================= memcheck/tests/oset_test (stderr) memcheck/tests/x86/scalar (stderr) --- 8,12 ---- ! == 230 tests, 7 stderr failures, 2 stdout failures ================= memcheck/tests/oset_test (stderr) + memcheck/tests/pointer-trace (stderr) memcheck/tests/x86/scalar (stderr) |
|
From: Tom H. <th...@cy...> - 2006-01-06 03:18:12
|
Nightly build on alvis ( i686, Red Hat 7.3 ) started at 2006-01-06 03:15:04 GMT
Results differ from 24 hours ago
Checking out valgrind source tree ... done
Configuring valgrind ... failed
Last 20 lines of verbose log follow echo
A valgrind/VEX/Makefile-icc
A valgrind/VEX/Makefile
A valgrind/VEX/LICENSE.README
U valgrind/VEX
Checked out external at revision 1532.
Checked out revision 5503.
Configuring valgrind ... cd valgrind && ./autogen.sh && ./configure --prefix=/tmp/valgrind.21788/Inst
running: aclocal
running: autoheader
running: automake -a
configure.in: installing `./install-sh'
configure.in: installing `./mkinstalldirs'
configure.in: installing `./missing'
configure.in:112: installing `./config.guess'
configure.in:112: installing `./config.sub'
addrcheck/Makefile.am: installing `./depcomp'
auxprogs/Makefile.am: installing `./compile'
DIST_SUBDIRS: variable `VG_ARCH_ALL' is used but `VG_ARCH_ALL' is undefined
error: while running 'automake -a'
=================================================
== Results from 24 hours ago ==
=================================================
Checking out valgrind source tree ... done
Configuring valgrind ... failed
Last 20 lines of verbose log follow echo
A valgrind/VEX/Makefile-icc
A valgrind/VEX/Makefile
A valgrind/VEX/LICENSE.README
U valgrind/VEX
Checked out external at revision 1532.
Checked out revision 5498.
Configuring valgrind ... cd valgrind && ./autogen.sh && ./configure --prefix=/tmp/valgrind.21788/Inst
running: aclocal
running: autoheader
running: automake -a
configure.in: installing `./install-sh'
configure.in: installing `./mkinstalldirs'
configure.in: installing `./missing'
configure.in:112: installing `./config.guess'
configure.in:112: installing `./config.sub'
addrcheck/Makefile.am: installing `./depcomp'
auxprogs/Makefile.am: installing `./compile'
DIST_SUBDIRS: variable `VG_ARCH_ALL' is used but `VG_ARCH_ALL' is undefined
error: while running 'automake -a'
=================================================
== Difference between 24 hours ago and now ==
=================================================
*** old.short Fri Jan 6 03:16:37 2006
--- new.short Fri Jan 6 03:18:05 2006
***************
*** 11,13 ****
! Checked out revision 5498.
Configuring valgrind ... cd valgrind && ./autogen.sh && ./configure --prefix=/tmp/valgrind.21788/Inst
--- 11,13 ----
! Checked out revision 5503.
Configuring valgrind ... cd valgrind && ./autogen.sh && ./configure --prefix=/tmp/valgrind.21788/Inst
|
|
From: Tom H. <th...@cy...> - 2006-01-06 03:12:56
|
Nightly build on gill ( x86_64, Fedora Core 2 ) started at 2006-01-06 03:00:03 GMT Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 230 tests, 5 stderr failures, 1 stdout failure ================= memcheck/tests/oset_test (stderr) memcheck/tests/x86/sse1_memory (stdout) none/tests/amd64/faultstatus (stderr) none/tests/fdleak_fcntl (stderr) none/tests/x86/faultstatus (stderr) none/tests/x86/int (stderr) |