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: Tom H. <to...@co...> - 2006-01-21 16:35:37
|
In message <43D...@us...>
Dave Nomura <dc...@us...> wrote:
> 1. if I installed valgrind into /usr/local but want to run a newer SVN
> version against some program is it sufficient to invoke valgrind:
> <SVN dir>/coregrind/valgrind <my_program>
> or
> alias vg <SVN dir>/coregrind/valgrind
> vg <my_program>
> I know that there are other libraries/shared objects that valgrind
> accesses and I thought that it might depend on the path used to
> invoke
> valgrind. If I use the VALGRIND_LAUNCHER or VALGRIND_LIB variables
> (set to a different valgrind release) for debugging but forget to
> unset them am I at risk for possibly
> running a different version of valgrind than I intended?
You should never need to set VALGRIND_LAUNCHER as the launcher (ie
the valgrind binary) does that.
If you are running outside the location where you told configure
you would be installing it then you need to set VALGRIND_LIB or you
will wind up running the installed version. The other option is to
configure with --prefix=/tmp/valgrind-test or something and then do
a make install and run /tmp/valgrind-test/bin/valgrind which is
what I tend to do.
> 2. I've been using the svn command listed on your website to pull over a
> newer version of valgrind. This command pulls over the entire
> trunk/* tree. Is there a way to just incrementally pull the files
> that changed or is the granularity of SVN just the entire source
> tree?
Just use "svn update" to update an existing tree with the latest changes.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|
|
From: Dave N. <dc...@us...> - 2006-01-21 16:06:42
|
Julian Seward wrote:
>>I saw 23 failures on my test run of the latest PPC64 Valgrind I got from
>>the Code Repository. Most of the failures were the same as reported by
>>Julian but I was also seeing some additional failures:
>
>
> Ok. You should really compare against the latest nightly build on
> Ceri's 970 (g5) which is posted to this list every night. Since there's
> been a lot of ppc hacking this last week, the test results have
> changed rapidly the past few days.
>
>
>>Here is my debugging analysis of the problem. Unless I have made a
>>mistake in locating the correct #includes/#defines I don't see anything
>>that looks host dependent.
>>
>>! valgrind: m_coredump/coredump-elf.c:267 (fill_prstatus): Assertion
>>'sizeof(*regs) == sizeof(prs->pr_reg)' failed.
>>[...]
>
>
> Good that you found that. But .. can you clarify which particular
> test is causing this failure, and what V version (3.1.0 or the svn
> trunk). It's not clear from your message.
>
> J
>
Here is what I wrote in my initial message:
>I saw 23 failures on my test run of the latest PPC64 Valgrind I got
>from the Code Repository. Most of the failures were the same as
>reported by Julian but I was also seeing some additional failures:
>memcheck/tests/badjump
>memcheck/tests/describe-block
>memcheck/tests/match-overrun
>none/tests/async-sigs
>none/tests/blockfault
>
>I saw the same failures when running the Valgrind 3.1.0 release.
The assertion error occurred in the list of tests listed above in a run
against an SVN snapshot taken on 1-18, as well as on the offical
Valgrind 3.1.0 release.
This list of failures was obtained by comparing my test results with
those posted on the mailing list on 1-19
Could you answer a couple of other unrelated questions?
1. if I installed valgrind into /usr/local but want to run a newer SVN
version against some program is it sufficient to invoke valgrind:
<SVN dir>/coregrind/valgrind <my_program>
or
alias vg <SVN dir>/coregrind/valgrind
vg <my_program>
I know that there are other libraries/shared objects that valgrind
accesses and I thought that it might depend on the path used to
invoke
valgrind. If I use the VALGRIND_LAUNCHER or VALGRIND_LIB variables
(set to a different valgrind release) for debugging but forget to
unset them am I at risk for possibly
running a different version of valgrind than I intended?
2. I've been using the svn command listed on your website to pull over a
newer version of valgrind. This command pulls over the entire
trunk/* tree. Is there a way to just incrementally pull the files
that changed or is the granularity of SVN just the entire source
tree?
|
|
From: <js...@ac...> - 2006-01-21 10:10:52
|
Nightly build on minnie ( SuSE 10.0, ppc32 ) started at 2006-01-21 05:00:02 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 == 184 tests, 10 stderr failures, 3 stdout failures ================= memcheck/tests/leak-cycle (stderr) memcheck/tests/leak-tree (stderr) memcheck/tests/leakotron (stdout) memcheck/tests/mempool (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/sigaltstack (stderr) memcheck/tests/stack_changes (stdout) memcheck/tests/stack_changes (stderr) memcheck/tests/xml1 (stderr) none/tests/faultstatus (stderr) none/tests/mremap (stderr) none/tests/ppc32/jm-fp (stdout) none/tests/ppc32/jm-fp (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 == 182 tests, 11 stderr failures, 3 stdout failures ================= memcheck/tests/leak-cycle (stderr) memcheck/tests/leak-tree (stderr) memcheck/tests/leakotron (stdout) memcheck/tests/mempool (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/sigaltstack (stderr) memcheck/tests/stack_changes (stdout) memcheck/tests/stack_changes (stderr) memcheck/tests/xml1 (stderr) none/tests/faultstatus (stderr) none/tests/fdleak_cmsg (stderr) none/tests/mremap (stderr) none/tests/ppc32/jm-fp (stdout) none/tests/ppc32/jm-fp (stderr) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Sat Jan 21 05:09:49 2006 --- new.short Sat Jan 21 05:19:20 2006 *************** *** 8,10 **** ! == 182 tests, 11 stderr failures, 3 stdout failures ================= memcheck/tests/leak-cycle (stderr) --- 8,10 ---- ! == 184 tests, 10 stderr failures, 3 stdout failures ================= memcheck/tests/leak-cycle (stderr) *************** *** 19,21 **** none/tests/faultstatus (stderr) - none/tests/fdleak_cmsg (stderr) none/tests/mremap (stderr) --- 19,20 ---- |
|
From: <js...@ac...> - 2006-01-21 04:03:36
|
Nightly build on phoenix ( SuSE 10.0 ) started at 2006-01-21 03:30:01 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 == 217 tests, 7 stderr failures, 0 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/scalar_supp (stderr) none/tests/x86/faultstatus (stderr) none/tests/x86/int (stderr) ================================================= == Results from 24 hours ago == ================================================= 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 == 215 tests, 6 stderr failures, 1 stdout failure ================= memcheck/tests/leak-tree (stderr) memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/scalar_supp (stderr) none/tests/mremap2 (stdout) none/tests/x86/faultstatus (stderr) none/tests/x86/int (stderr) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Sat Jan 21 03:46:30 2006 --- new.short Sat Jan 21 04:04:13 2006 *************** *** 10,13 **** ! == 215 tests, 6 stderr failures, 1 stdout failure ================= memcheck/tests/leak-tree (stderr) memcheck/tests/stack_switch (stderr) --- 10,14 ---- ! == 217 tests, 7 stderr failures, 0 stdout failures ================= memcheck/tests/leak-tree (stderr) + memcheck/tests/pointer-trace (stderr) memcheck/tests/stack_switch (stderr) *************** *** 15,17 **** memcheck/tests/x86/scalar_supp (stderr) - none/tests/mremap2 (stdout) none/tests/x86/faultstatus (stderr) --- 16,17 ---- |
|
From: <js...@ac...> - 2006-01-21 03:54:43
|
Nightly build on g5 ( YDL 4.0, ppc970 ) started at 2006-01-21 04:40:00 CET 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 == 187 tests, 6 stderr failures, 1 stdout failure ================= memcheck/tests/leak-cycle (stderr) memcheck/tests/leak-tree (stderr) memcheck/tests/leakotron (stdout) memcheck/tests/pointer-trace (stderr) none/tests/faultstatus (stderr) none/tests/fdleak_fcntl (stderr) none/tests/mremap (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 == 185 tests, 87 stderr failures, 28 stdout failures ================= memcheck/tests/addressable (stdout) memcheck/tests/addressable (stderr) memcheck/tests/badaddrvalue (stdout) memcheck/tests/badaddrvalue (stderr) memcheck/tests/badfree-2trace (stderr) memcheck/tests/badfree (stderr) memcheck/tests/badjump (stderr) memcheck/tests/badjump2 (stderr) memcheck/tests/badloop (stderr) memcheck/tests/badpoll (stderr) memcheck/tests/badrw (stderr) memcheck/tests/brk (stderr) memcheck/tests/brk2 (stderr) memcheck/tests/buflen_check (stderr) memcheck/tests/clientperm (stdout) memcheck/tests/clientperm (stderr) memcheck/tests/custom_alloc (stderr) memcheck/tests/describe-block (stderr) memcheck/tests/doublefree (stderr) memcheck/tests/erringfds (stdout) memcheck/tests/erringfds (stderr) memcheck/tests/error_counts (stdout) memcheck/tests/errs1 (stderr) memcheck/tests/execve (stderr) memcheck/tests/execve2 (stderr) memcheck/tests/exitprog (stderr) memcheck/tests/fprw (stderr) memcheck/tests/fwrite (stderr) memcheck/tests/inits (stderr) memcheck/tests/inline (stdout) memcheck/tests/inline (stderr) memcheck/tests/leak-0 (stderr) memcheck/tests/leak-cycle (stderr) memcheck/tests/leak-regroot (stderr) memcheck/tests/leak-tree (stderr) memcheck/tests/leakotron (stdout) memcheck/tests/malloc1 (stderr) memcheck/tests/malloc2 (stderr) memcheck/tests/malloc3 (stdout) memcheck/tests/malloc3 (stderr) memcheck/tests/malloc_usable (stderr) memcheck/tests/manuel1 (stdout) memcheck/tests/manuel1 (stderr) memcheck/tests/manuel2 (stdout) memcheck/tests/manuel2 (stderr) memcheck/tests/manuel3 (stderr) memcheck/tests/match-overrun (stderr) memcheck/tests/memalign2 (stderr) memcheck/tests/memalign_test (stderr) memcheck/tests/memcmptest (stdout) memcheck/tests/memcmptest (stderr) memcheck/tests/mempool (stderr) memcheck/tests/mismatches (stderr) memcheck/tests/mmaptest (stderr) memcheck/tests/nanoleak (stderr) memcheck/tests/nanoleak_supp (stderr) memcheck/tests/new_nothrow (stderr) memcheck/tests/new_override (stdout) memcheck/tests/new_override (stderr) memcheck/tests/null_socket (stderr) memcheck/tests/oset_test (stdout) memcheck/tests/oset_test (stderr) memcheck/tests/overlap (stdout) memcheck/tests/overlap (stderr) memcheck/tests/partial_load_dflt (stderr) memcheck/tests/partial_load_ok (stderr) memcheck/tests/partiallydefinedeq (stdout) memcheck/tests/partiallydefinedeq (stderr) memcheck/tests/pipe (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/post-syscall (stdout) memcheck/tests/post-syscall (stderr) memcheck/tests/realloc1 (stderr) memcheck/tests/realloc2 (stderr) memcheck/tests/realloc3 (stderr) memcheck/tests/sigaltstack (stderr) memcheck/tests/sigkill (stderr) memcheck/tests/signal2 (stdout) memcheck/tests/signal2 (stderr) memcheck/tests/sigprocmask (stderr) memcheck/tests/stack_changes (stdout) memcheck/tests/stack_changes (stderr) memcheck/tests/stack_switch (stderr) memcheck/tests/str_tester (stderr) memcheck/tests/strchr (stderr) memcheck/tests/supp1 (stderr) memcheck/tests/supp2 (stderr) memcheck/tests/supp_unknown (stderr) memcheck/tests/suppfree (stderr) memcheck/tests/toobig-allocs (stderr) memcheck/tests/trivialleak (stderr) memcheck/tests/with-space (stdout) memcheck/tests/with-space (stderr) memcheck/tests/wrap1 (stdout) memcheck/tests/wrap1 (stderr) memcheck/tests/wrap2 (stdout) memcheck/tests/wrap2 (stderr) memcheck/tests/wrap3 (stdout) memcheck/tests/wrap3 (stderr) memcheck/tests/wrap4 (stdout) memcheck/tests/wrap4 (stderr) memcheck/tests/wrap5 (stdout) memcheck/tests/wrap5 (stderr) memcheck/tests/wrap6 (stdout) memcheck/tests/wrap6 (stderr) memcheck/tests/writev (stderr) memcheck/tests/xml1 (stdout) memcheck/tests/xml1 (stderr) memcheck/tests/zeropage (stdout) memcheck/tests/zeropage (stderr) none/tests/faultstatus (stderr) none/tests/fdleak_cmsg (stderr) none/tests/fdleak_fcntl (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Sat Jan 21 04:46:35 2006 --- new.short Sat Jan 21 04:54:37 2006 *************** *** 8,125 **** ! == 185 tests, 87 stderr failures, 28 stdout failures ================= ! memcheck/tests/addressable (stdout) ! memcheck/tests/addressable (stderr) ! memcheck/tests/badaddrvalue (stdout) ! memcheck/tests/badaddrvalue (stderr) ! memcheck/tests/badfree-2trace (stderr) ! memcheck/tests/badfree (stderr) ! memcheck/tests/badjump (stderr) ! memcheck/tests/badjump2 (stderr) ! memcheck/tests/badloop (stderr) ! memcheck/tests/badpoll (stderr) ! memcheck/tests/badrw (stderr) ! memcheck/tests/brk (stderr) ! memcheck/tests/brk2 (stderr) ! memcheck/tests/buflen_check (stderr) ! memcheck/tests/clientperm (stdout) ! memcheck/tests/clientperm (stderr) ! memcheck/tests/custom_alloc (stderr) ! memcheck/tests/describe-block (stderr) ! memcheck/tests/doublefree (stderr) ! memcheck/tests/erringfds (stdout) ! memcheck/tests/erringfds (stderr) ! memcheck/tests/error_counts (stdout) ! memcheck/tests/errs1 (stderr) ! memcheck/tests/execve (stderr) ! memcheck/tests/execve2 (stderr) ! memcheck/tests/exitprog (stderr) ! memcheck/tests/fprw (stderr) ! memcheck/tests/fwrite (stderr) ! memcheck/tests/inits (stderr) ! memcheck/tests/inline (stdout) ! memcheck/tests/inline (stderr) ! memcheck/tests/leak-0 (stderr) memcheck/tests/leak-cycle (stderr) - memcheck/tests/leak-regroot (stderr) memcheck/tests/leak-tree (stderr) memcheck/tests/leakotron (stdout) - memcheck/tests/malloc1 (stderr) - memcheck/tests/malloc2 (stderr) - memcheck/tests/malloc3 (stdout) - memcheck/tests/malloc3 (stderr) - memcheck/tests/malloc_usable (stderr) - memcheck/tests/manuel1 (stdout) - memcheck/tests/manuel1 (stderr) - memcheck/tests/manuel2 (stdout) - memcheck/tests/manuel2 (stderr) - memcheck/tests/manuel3 (stderr) - memcheck/tests/match-overrun (stderr) - memcheck/tests/memalign2 (stderr) - memcheck/tests/memalign_test (stderr) - memcheck/tests/memcmptest (stdout) - memcheck/tests/memcmptest (stderr) - memcheck/tests/mempool (stderr) - memcheck/tests/mismatches (stderr) - memcheck/tests/mmaptest (stderr) - memcheck/tests/nanoleak (stderr) - memcheck/tests/nanoleak_supp (stderr) - memcheck/tests/new_nothrow (stderr) - memcheck/tests/new_override (stdout) - memcheck/tests/new_override (stderr) - memcheck/tests/null_socket (stderr) - memcheck/tests/oset_test (stdout) - memcheck/tests/oset_test (stderr) - memcheck/tests/overlap (stdout) - memcheck/tests/overlap (stderr) - memcheck/tests/partial_load_dflt (stderr) - memcheck/tests/partial_load_ok (stderr) - memcheck/tests/partiallydefinedeq (stdout) - memcheck/tests/partiallydefinedeq (stderr) - memcheck/tests/pipe (stderr) memcheck/tests/pointer-trace (stderr) - memcheck/tests/post-syscall (stdout) - memcheck/tests/post-syscall (stderr) - memcheck/tests/realloc1 (stderr) - memcheck/tests/realloc2 (stderr) - memcheck/tests/realloc3 (stderr) - memcheck/tests/sigaltstack (stderr) - memcheck/tests/sigkill (stderr) - memcheck/tests/signal2 (stdout) - memcheck/tests/signal2 (stderr) - memcheck/tests/sigprocmask (stderr) - memcheck/tests/stack_changes (stdout) - memcheck/tests/stack_changes (stderr) - memcheck/tests/stack_switch (stderr) - memcheck/tests/str_tester (stderr) - memcheck/tests/strchr (stderr) - memcheck/tests/supp1 (stderr) - memcheck/tests/supp2 (stderr) - memcheck/tests/supp_unknown (stderr) - memcheck/tests/suppfree (stderr) - memcheck/tests/toobig-allocs (stderr) - memcheck/tests/trivialleak (stderr) - memcheck/tests/with-space (stdout) - memcheck/tests/with-space (stderr) - memcheck/tests/wrap1 (stdout) - memcheck/tests/wrap1 (stderr) - memcheck/tests/wrap2 (stdout) - memcheck/tests/wrap2 (stderr) - memcheck/tests/wrap3 (stdout) - memcheck/tests/wrap3 (stderr) - memcheck/tests/wrap4 (stdout) - memcheck/tests/wrap4 (stderr) - memcheck/tests/wrap5 (stdout) - memcheck/tests/wrap5 (stderr) - memcheck/tests/wrap6 (stdout) - memcheck/tests/wrap6 (stderr) - memcheck/tests/writev (stderr) - memcheck/tests/xml1 (stdout) - memcheck/tests/xml1 (stderr) - memcheck/tests/zeropage (stdout) - memcheck/tests/zeropage (stderr) none/tests/faultstatus (stderr) - none/tests/fdleak_cmsg (stderr) none/tests/fdleak_fcntl (stderr) none/tests/mremap (stderr) - none/tests/mremap2 (stdout) --- 8,17 ---- ! == 187 tests, 6 stderr failures, 1 stdout failure ================= memcheck/tests/leak-cycle (stderr) memcheck/tests/leak-tree (stderr) memcheck/tests/leakotron (stdout) memcheck/tests/pointer-trace (stderr) none/tests/faultstatus (stderr) none/tests/fdleak_fcntl (stderr) none/tests/mremap (stderr) |
|
From: <sv...@va...> - 2006-01-21 03:47:49
|
Author: sewardj Date: 2006-01-21 03:47:44 +0000 (Sat, 21 Jan 2006) New Revision: 5578 Log: Update. Modified: trunk/docs/internals/3_1_BUGSTATUS.txt Modified: trunk/docs/internals/3_1_BUGSTATUS.txt =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/docs/internals/3_1_BUGSTATUS.txt 2006-01-20 21:46:03 UTC (rev 5= 577) +++ trunk/docs/internals/3_1_BUGSTATUS.txt 2006-01-21 03:47:44 UTC (rev 5= 578) @@ -38,3 +38,21 @@ vx1521/2 pending 119297 Incorrect error message for sse code v5500 pending n-i-bz misaligned path word-size bug in mc_main.c v5514 pending 119914 more stabs problems + +119482: mtfsb1 ppc instruction not implemented + fixed (head?) (vx1531, check) + +119973 Sun JVM problems + +120277 unimplemented PPC floating point instructions: fres, fctid, + fctidz, frsqrte + +120345 another stabs bug (maybe =3D=3D 119914 ?) + + + + +don't forget: +Dave Nomura extra suppression (dev, Tue Jan 17 00:14:30 2006) +Control-Z bug +Sun JVM hangs; possible sigcontext problem |
|
From: Tom H. <to...@co...> - 2006-01-21 03:43:11
|
Nightly build on dunsmere ( athlon, Fedora Core 4 ) started at 2006-01-21 03:30:07 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 == 219 tests, 8 stderr failures, 1 stdout failure ================= 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/scalar_supp (stderr) memcheck/tests/x86/sse1_memory (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 == 217 tests, 8 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/scalar_supp (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 Sat Jan 21 03:36:40 2006 --- new.short Sat Jan 21 03:43:02 2006 *************** *** 8,10 **** ! == 217 tests, 8 stderr failures, 2 stdout failures ================= memcheck/tests/leak-tree (stderr) --- 8,10 ---- ! == 219 tests, 8 stderr failures, 1 stdout failure ================= memcheck/tests/leak-tree (stderr) *************** *** 16,18 **** memcheck/tests/x86/sse1_memory (stdout) - none/tests/mremap2 (stdout) none/tests/x86/faultstatus (stderr) --- 16,17 ---- |
|
From: Tom H. <th...@cy...> - 2006-01-21 03:29:48
|
Nightly build on gill ( x86_64, Fedora Core 2 ) started at 2006-01-21 03:00:02 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 == 238 tests, 7 stderr failures, 2 stdout failures ================= memcheck/tests/stack_switch (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/fdleak_fcntl (stderr) none/tests/tls (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 == 236 tests, 7 stderr failures, 2 stdout failures ================= memcheck/tests/stack_switch (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/fdleak_fcntl (stderr) none/tests/tls (stdout) none/tests/x86/faultstatus (stderr) none/tests/x86/int (stderr) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Sat Jan 21 03:14:41 2006 --- new.short Sat Jan 21 03:29:38 2006 *************** *** 8,10 **** ! == 236 tests, 7 stderr failures, 2 stdout failures ================= memcheck/tests/stack_switch (stderr) --- 8,10 ---- ! == 238 tests, 7 stderr failures, 2 stdout failures ================= memcheck/tests/stack_switch (stderr) |
|
From: Tom H. <th...@cy...> - 2006-01-21 03:29:27
|
Nightly build on alvis ( i686, Red Hat 7.3 ) started at 2006-01-21 03:15:02 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 == 218 tests, 21 stderr failures, 2 stdout failures ================= memcheck/tests/addressable (stderr) memcheck/tests/badjump (stderr) memcheck/tests/describe-block (stderr) memcheck/tests/erringfds (stderr) memcheck/tests/leak-0 (stderr) memcheck/tests/leak-cycle (stderr) memcheck/tests/leak-regroot (stderr) memcheck/tests/leak-tree (stderr) memcheck/tests/leakotron (stdout) memcheck/tests/match-overrun (stderr) memcheck/tests/mempool (stderr) memcheck/tests/partial_load_dflt (stderr) memcheck/tests/partial_load_ok (stderr) memcheck/tests/partiallydefinedeq (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/sigkill (stderr) memcheck/tests/stack_changes (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/scalar_supp (stderr) memcheck/tests/x86/sse1_memory (stdout) memcheck/tests/xml1 (stderr) 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 == 216 tests, 21 stderr failures, 2 stdout failures ================= memcheck/tests/addressable (stderr) memcheck/tests/badjump (stderr) memcheck/tests/describe-block (stderr) memcheck/tests/erringfds (stderr) memcheck/tests/leak-0 (stderr) memcheck/tests/leak-cycle (stderr) memcheck/tests/leak-regroot (stderr) memcheck/tests/leak-tree (stderr) memcheck/tests/leakotron (stdout) memcheck/tests/match-overrun (stderr) memcheck/tests/mempool (stderr) memcheck/tests/partial_load_dflt (stderr) memcheck/tests/partial_load_ok (stderr) memcheck/tests/partiallydefinedeq (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/sigkill (stderr) memcheck/tests/stack_changes (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/scalar_supp (stderr) memcheck/tests/x86/sse1_memory (stdout) memcheck/tests/xml1 (stderr) none/tests/x86/faultstatus (stderr) none/tests/x86/int (stderr) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Sat Jan 21 03:22:23 2006 --- new.short Sat Jan 21 03:29:20 2006 *************** *** 8,10 **** ! == 216 tests, 21 stderr failures, 2 stdout failures ================= memcheck/tests/addressable (stderr) --- 8,10 ---- ! == 218 tests, 21 stderr failures, 2 stdout failures ================= memcheck/tests/addressable (stderr) |
|
From: Tom H. <th...@cy...> - 2006-01-21 03:23:08
|
Nightly build on dellow ( x86_64, Fedora Core 4 ) started at 2006-01-21 03:10:07 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 == 238 tests, 6 stderr failures, 1 stdout failure ================= 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/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 == 236 tests, 5 stderr failures, 2 stdout failures ================= 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 Sat Jan 21 03:17:19 2006 --- new.short Sat Jan 21 03:22:59 2006 *************** *** 8,10 **** ! == 236 tests, 5 stderr failures, 2 stdout failures ================= memcheck/tests/x86/scalar (stderr) --- 8,11 ---- ! == 238 tests, 6 stderr failures, 1 stdout failure ================= ! memcheck/tests/pointer-trace (stderr) memcheck/tests/x86/scalar (stderr) *************** *** 13,15 **** none/tests/amd64/faultstatus (stderr) - none/tests/mremap2 (stdout) none/tests/x86/faultstatus (stderr) --- 14,15 ---- |
|
From: Julian S. <js...@ac...> - 2006-01-21 03:19:42
|
> {
> int i = 4;
> static int j = 5;
> ELAN_EVENT *e = elan_get(elan_base->state,&j,&i,sizeof(int),0);
> printf("i is %d\n",i);
> elan_wait(e,ELAN_POLL_EVENT);
> printf("i is %d\n",i);
> }
>
> The prototype for elan_get is this, it starts a simple network read:
> extern ELAN_EVENT *elan_get (ELAN_STATE *state, void *source, void
> *target, size_t len, uint32_t srcvp);
>
> In this code the result of first printf is undefined and the second one
> will print 5. I was hoping Valgrind could be made to flag an error on
> the first printf.
I think you're hoping for a bit much. You assigned a value to i
at the start so it's defined.
But if I read this correctly, elan_get just remembers &i (presumably
in ELAN_EVENT which is some kind of handle) and writes the actual
amount of received data there in elan_wait. So why don't you
start with no value in i - then V will consider it undefined until
elan_wait writes it.
> {
> int i;
> static int j = 5;
> [...]
J
|
|
From: Tom H. <th...@cy...> - 2006-01-21 03:18:37
|
Nightly build on aston ( x86_64, Fedora Core 3 ) started at 2006-01-21 03:05:13 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 == 238 tests, 6 stderr failures, 1 stdout failure ================= memcheck/tests/stack_switch (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/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 == 236 tests, 6 stderr failures, 2 stdout failures ================= memcheck/tests/stack_switch (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 Sat Jan 21 03:12:16 2006 --- new.short Sat Jan 21 03:18:31 2006 *************** *** 8,10 **** ! == 236 tests, 6 stderr failures, 2 stdout failures ================= memcheck/tests/stack_switch (stderr) --- 8,10 ---- ! == 238 tests, 6 stderr failures, 1 stdout failure ================= memcheck/tests/stack_switch (stderr) *************** *** 14,16 **** none/tests/amd64/faultstatus (stderr) - none/tests/mremap2 (stdout) none/tests/x86/faultstatus (stderr) --- 14,15 ---- |
|
From: Julian S. <js...@ac...> - 2006-01-21 03:11:07
|
On Friday 20 January 2006 01:12, Uttam Pawar wrote: > Hi All, > > Here is 2nd cleanup patch. Variable 'human_readable' is always true, so > the following conditional assignment is really not necessary. True, but it's not harmful either as the compiler will fold away the unused side. It's probably there to make debugging easier. J |
|
From: Julian S. <js...@ac...> - 2006-01-21 03:06:10
|
> I saw 23 failures on my test run of the latest PPC64 Valgrind I got from > the Code Repository. Most of the failures were the same as reported by > Julian but I was also seeing some additional failures: Ok. You should really compare against the latest nightly build on Ceri's 970 (g5) which is posted to this list every night. Since there's been a lot of ppc hacking this last week, the test results have changed rapidly the past few days. > Here is my debugging analysis of the problem. Unless I have made a > mistake in locating the correct #includes/#defines I don't see anything > that looks host dependent. > > ! valgrind: m_coredump/coredump-elf.c:267 (fill_prstatus): Assertion > 'sizeof(*regs) == sizeof(prs->pr_reg)' failed. > [...] Good that you found that. But .. can you clarify which particular test is causing this failure, and what V version (3.1.0 or the svn trunk). It's not clear from your message. J |
|
From: Julian S. <js...@ac...> - 2006-01-21 02:58:01
|
Ashley
> #define V_START_GET(TARGET,LEN) \
> do { \
> VALGRIND_CHECK_WRITABLE(TARGET,LEN); \
> VALGRIND_MAKE_WRITABLE(TARGET,LEN); \
> } while (0)
>
> #define V_END_GET(TARGET,LEN) \
> do { \
> VALGRIND_MAKE_READABLE(TARGET,LEN); \
> } while (0)
>
> #define V_START_PUT(TARGET,LEN) \
> do { \
> VALGRIND_CHECK_READABLE(TARGET,LEN); \
> } while (0)
>
> Now my questions are mainly about the asynchronous get, it checks that
> the buffer it's been given is valid (VALGRIND_CHECK_WRITABLE) and
> temporarily marks it as addressable but undefined whilst the data is
> arriving. My question is what does VALGRIND_MAKE_WRITABLE do if the
> buffer isn't addressable before it's called. I don't want it to mark a
> buffer as addressable when it isn't, only to mark it as undefined while
> the network transfer is underway. Am I doing the right thing here?
My impression is that what you need to do is:
- at the initial request (V_START_GET), first check the recv
buffer is addressible (VALGRIND_CHECK_WRITABLE), and then
force it to be unaddressible so V will yelp if anyone pokes
there (VALGRIND_MAKE_NOACCESS)
- when the request completes and you know how much data really
arrived, do VALGRIND_MAKE_READABLE. This marks the area as
both addressible and containing defined data.
Does that make sense?
> Another request I have is can error reports from client requests include
> a byte counter in the output, in the case of buffer over-runs it would
> really help, in this case it was reading eight bytes from a malloced
> buffer of four although it's impossible to see that from the output.
>
> ==26004== Uninitialised byte(s) found during client check request
> ==26004== at 0x40641F3: elan_hbcast (common/group_hbcast.c:820)
> ==26004== by 0x8048661: main
> (in /opt/ashley/auto-build/quadrics/qstests/a.out)
> ==26004== Address 0x5ABDFC0 is 0 bytes inside a block of size 4 alloc'd
> ==26004== at 0x400446D: malloc (vg_replace_malloc.c:149)
> ==26004== by 0x804863E: main
> (in /opt/ashley/auto-build/quadrics/qstests/a.out)
The problem here is there are two possible sources of error and V can
only report one or the other. Let . mean a byte which is unaddressible
and X mean one which is addressible but is undefined. Your buffer
looks like this
.......XXXX......
^
a
Now you do VALGRIND_CHECK_READABLE(a,8). Should it complain that
a[0 .. 3] are undefined, or that a[4 .. 7] are unaddressible? Both
are legitimate complaints. I think the reason for the confusion is
that it's reporting the former and you're expecting the latter.
If those four bytes were defined then it should indeed complain
about a[4..7] being unaddressible.
Could be I'm way off base, but I _think_ that's the behaviour.
J
|
|
From: Julian S. <js...@ac...> - 2006-01-21 02:47:18
|
On Wednesday 18 January 2006 15:19, Josef Weidendorfer wrote:
> On Wednesday 18 January 2006 06:24, Julian Seward wrote:
> > to the post-actions since both are in the same function. Recursion and
> > I think longjmping still work (perhaps not on ppc64).
>
> Longjumping will skip the frame of the wrapper function, too.
> So post-actions are not called.
>
> I am not sure this is a problem in practice.
For x86/amd64/ppc32, function wrapping is simple, conceptually:
when a wrapped/redirected function is called, V runs instead the
replacement function, and at that instant also it writes into a
pseudo-register (guest_NRADDR) the address of the un-redirected
function ("NRADDR" == Non-Redirected Address). The wrapper
function can get hold of this address and call it to get to the
original.
So function wrapping only requires magic at entry to the wrapper,
not at exit. This means longjumping and recursion work right.
On ppc64-linux it is not so simple. For each function, %r2 must
point to a constant pool ("table of contents") which is specific to
that function, or at least to that shared object.
Therefore, when diverting to the wrapper, valgrind must reload
r2 with a new value which is correct for the wrapper*. When the
wrapper returns it must restore r2 to what it was before. This
means that V has to keep a shadow stack of (pc,r2) pairs, one
for each nested wrapper which is active, and carefully save and
restore r2 values. This means if there is a longjmp in a wrapper
it will go wrong, because this stack will be out of sync.
J
* even the problem of figuring out the correct r2 for a given
function is not simple, requires some rather fragile extensions
to the symbol table reader
|
|
From: Julian S. <js...@ac...> - 2006-01-21 02:29:21
|
Dave
> but in the offical release valgrind -v output the error messages are
> generated before reading in libc.2.3.4.so I thought the problems I was
> seeing might be related to the fact that the libc archive was read in
> too late.
The default suppressions are quite fragile, because there's a wide
variability in the number of symbols attached to libc.co and ld.so,
depending on the Linux distro you're using. I'd hazard a guess that
you're using SLES9, which is a distro we didn't test 3.1.0 on as
we didn't have access to a machine running it.
> If you think this analysis is correct, then my suggested fix for this is
> to add an additional entry in glibc-2.3.supp:
> -{
> - index-not-intercepted-early-enough-HACK-4
> - Memcheck:Cond
> - fun:index
> - fun:expand_dynamic_string_token
> -}
Seems reasonable.
--------
By far the most effective way to ensure V works well on your
system is to set up the nightly build system on it. Monitoring
and fixing failures the nightly builds report to the dev list
really helps keep the system working well.
It's easy:
check out from svn, copy the nightly/ directory somewhere else
and read nightly/README.txt. This will do builds of the svn trunk
and sometimes picks up stuff which should be merged to the stable
(3.1.X) branch.
J
|