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
(25) |
2
(25) |
3
(5) |
4
(13) |
|
5
(4) |
6
(8) |
7
(6) |
8
|
9
(10) |
10
(15) |
11
(9) |
|
12
(14) |
13
(10) |
14
(24) |
15
(41) |
16
(13) |
17
(9) |
18
(3) |
|
19
(10) |
20
(11) |
21
(28) |
22
(36) |
23
(52) |
24
(36) |
25
(12) |
|
26
(31) |
27
(27) |
28
(20) |
29
(15) |
30
(22) |
31
(17) |
|
|
From: <sv...@va...> - 2009-07-30 23:36:54
|
Author: njn
Date: 2009-07-31 00:36:43 +0100 (Fri, 31 Jul 2009)
New Revision: 10669
Log:
Don't bother printing "My PID" when logging to a file or socket, as that
value is shown at the start of every output line.
Modified:
trunk/coregrind/m_main.c
Modified: trunk/coregrind/m_main.c
===================================================================
--- trunk/coregrind/m_main.c 2009-07-30 23:35:11 UTC (rev 10668)
+++ trunk/coregrind/m_main.c 2009-07-30 23:36:43 UTC (rev 10669)
@@ -1052,7 +1052,7 @@
}
if (!VG_(clo_xml) && VG_(clo_verbosity) > 0 && !logging_to_fd) {
- VG_(umsg)("My PID: %d, parent PID: %d\n", VG_(getpid)(), VG_(getppid)());
+ VG_(umsg)("Parent PID: %d\n", VG_(getppid)());
}
else
if (VG_(clo_xml)) {
|
|
From: <sv...@va...> - 2009-07-30 23:35:27
|
Author: njn
Date: 2009-07-31 00:35:11 +0100 (Fri, 31 Jul 2009)
New Revision: 10668
Log:
Now that we always print the command, no need to reprint it when logging to
file or a socket. And tweak how the PIDs are printed.
Modified:
trunk/coregrind/m_main.c
Modified: trunk/coregrind/m_main.c
===================================================================
--- trunk/coregrind/m_main.c 2009-07-30 23:14:55 UTC (rev 10667)
+++ trunk/coregrind/m_main.c 2009-07-30 23:35:11 UTC (rev 10668)
@@ -1052,14 +1052,7 @@
}
if (!VG_(clo_xml) && VG_(clo_verbosity) > 0 && !logging_to_fd) {
- VG_(umsg)("\n");
- VG_(umsg)("My PID = %d, parent PID = %d. Prog and args are:\n",
- VG_(getpid)(), VG_(getppid)() );
- if (VG_(args_the_exename))
- VG_(umsg)(" %s\n", VG_(args_the_exename));
- for (i = 0; i < VG_(sizeXA)( VG_(args_for_client) ); i++)
- VG_(umsg)(" %s\n",
- * (HChar**) VG_(indexXA)( VG_(args_for_client), i ));
+ VG_(umsg)("My PID: %d, parent PID: %d\n", VG_(getpid)(), VG_(getppid)());
}
else
if (VG_(clo_xml)) {
@@ -1111,7 +1104,7 @@
// Empty line after the preamble
if (VG_(clo_verbosity) > 0)
- VG_(message)(Vg_UserMsg, "\n");
+ VG_(umsg)("\n");
if (VG_(clo_xml))
VG_(printf_xml)("\n");
|
|
From: <sv...@va...> - 2009-07-30 23:15:12
|
Author: njn
Date: 2009-07-31 00:14:55 +0100 (Fri, 31 Jul 2009)
New Revision: 10667
Log:
Don't print the command in the preamble with --xml=yes.
Modified:
trunk/coregrind/m_main.c
Modified: trunk/coregrind/m_main.c
===================================================================
--- trunk/coregrind/m_main.c 2009-07-30 22:21:24 UTC (rev 10666)
+++ trunk/coregrind/m_main.c 2009-07-30 23:14:55 UTC (rev 10667)
@@ -1028,9 +1028,9 @@
==9717== fffffffffffffffffffffffffffff 1 2 3 \
==9717== bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
*/
- VG_(umsg)("Command: ");
+ umsg_or_xml("Command: ");
if (VG_(args_the_exename))
- VG_(umsg)("%s", VG_(args_the_exename));
+ umsg_or_xml("%s", VG_(args_the_exename));
n = 0;
for (i = 0; i < VG_(sizeXA)( VG_(args_for_client) ); i++) {
HChar* s = *(HChar**)VG_(indexXA)( VG_(args_for_client), i );
@@ -1043,9 +1043,9 @@
VG_(umsg)("\n ");
n = slen;
}
- VG_(umsg)(" %s", s);
+ umsg_or_xml(" %s", s);
}
- VG_(umsg)("\n");
+ umsg_or_xml("\n");
if (VG_(clo_xml))
VG_(printf_xml)("</preamble>\n");
|
|
From: <sv...@va...> - 2009-07-30 22:21:43
|
Author: njn Date: 2009-07-30 23:21:24 +0100 (Thu, 30 Jul 2009) New Revision: 10666 Log: Avoid ampersands that seem to be causing XML-to-PDF conversion troubles. Modified: trunk/exp-ptrcheck/docs/pc-manual.xml Modified: trunk/exp-ptrcheck/docs/pc-manual.xml =================================================================== --- trunk/exp-ptrcheck/docs/pc-manual.xml 2009-07-30 04:48:05 UTC (rev 10665) +++ trunk/exp-ptrcheck/docs/pc-manual.xml 2009-07-30 22:21:24 UTC (rev 10666) @@ -5,8 +5,8 @@ <chapter id="pc-manual" - xreflabel="Ptrcheck: an experimental heap, stack & global array overrun detector"> - <title>Ptrcheck: an experimental heap, stack & global array overrun detector</title> + xreflabel="Ptrcheck: an experimental heap, stack and global array overrun detector"> + <title>Ptrcheck: an experimental heap, stack and global array overrun detector</title> <para>To use this tool, you must specify <option>--tool=exp-ptrcheck</option> on the Valgrind |
|
From: Nicholas N. <n.n...@gm...> - 2009-07-30 17:27:13
|
Nightly build on ocean32 ( Ubuntu 9.04, x86_64 (32-bit only) )
Started at 2009-07-31 03:00:01 EST
Ended at 2009-07-31 03:26:56 EST
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
== 482 tests, 9 stderr failures, 1 stdout failure, 0 post failures ==
memcheck/tests/origin5-bz2 (stderr)
none/tests/empty-exe (stderr)
none/tests/shell (stdout)
none/tests/shell (stderr)
none/tests/shell_valid1 (stderr)
none/tests/shell_valid2 (stderr)
none/tests/shell_valid3 (stderr)
none/tests/shell_zerolength (stderr)
helgrind/tests/tc06_two_races_xml (stderr)
exp-ptrcheck/tests/supp (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
== 481 tests, 9 stderr failures, 1 stdout failure, 0 post failures ==
memcheck/tests/origin5-bz2 (stderr)
none/tests/empty-exe (stderr)
none/tests/shell (stdout)
none/tests/shell (stderr)
none/tests/shell_valid1 (stderr)
none/tests/shell_valid2 (stderr)
none/tests/shell_valid3 (stderr)
none/tests/shell_zerolength (stderr)
helgrind/tests/tc06_two_races_xml (stderr)
exp-ptrcheck/tests/supp (stderr)
=================================================
== Difference between 24 hours ago and now ==
=================================================
*** old.short Fri Jul 31 03:14:06 2009
--- new.short Fri Jul 31 03:26:56 2009
***************
*** 8,10 ****
! == 481 tests, 9 stderr failures, 1 stdout failure, 0 post failures ==
memcheck/tests/origin5-bz2 (stderr)
--- 8,10 ----
! == 482 tests, 9 stderr failures, 1 stdout failure, 0 post failures ==
memcheck/tests/origin5-bz2 (stderr)
=================================================
./valgrind-new/exp-ptrcheck/tests/supp.stderr.diff
=================================================
--- supp.stderr.exp 2009-07-31 03:14:38.000000000 +1000
+++ supp.stderr.out 2009-07-31 03:26:52.000000000 +1000
@@ -1,7 +1,7 @@
Syscall param write(buf) is non-contiguous
- at 0x........: write (in /...libc...)
- by 0x........: main (supp.c:16)
+ at 0x........: ??? (in /lib32/ld-2.9.so)
+ by 0x........: (below main)
First byte (0x........) is 3 bytes inside a 6-byte block alloc'd
at 0x........: malloc (vg_replace_malloc.c:...)
by 0x........: main (supp.c:12)
=================================================
./valgrind-new/helgrind/tests/tc06_two_races_xml.stderr.diff
=================================================
--- tc06_two_races_xml.stderr.exp 2009-07-31 03:14:29.000000000 +1000
+++ tc06_two_races_xml.stderr.out 2009-07-31 03:24:20.000000000 +1000
@@ -43,16 +43,6 @@
<frame>
<ip>0x........</ip>
<obj>...</obj>
- <fn>do_clone</fn>
- </frame>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
- <fn>pthread_create@@GLIBC_2.2.5</fn>
- </frame>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
<fn>pthread_create_WRK</fn>
<dir>...</dir>
<file>hg_intercepts.c</file>
=================================================
./valgrind-new/memcheck/tests/origin5-bz2.stderr.diff-glibc25-amd64
=================================================
--- origin5-bz2.stderr.exp-glibc25-amd64 2009-07-31 03:15:23.000000000 +1000
+++ origin5-bz2.stderr.out 2009-07-31 03:21:47.000000000 +1000
@@ -11,7 +11,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: handle_compress (origin5-bz2.c:4686)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
@@ -19,7 +19,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: handle_compress (origin5-bz2.c:4686)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
@@ -27,7 +27,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: mainSort (origin5-bz2.c:2820)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -38,7 +38,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: mainSort (origin5-bz2.c:2823)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -49,7 +49,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: mainSort (origin5-bz2.c:2854)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -60,7 +60,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: mainSort (origin5-bz2.c:2858)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -71,7 +71,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: mainSort (origin5-bz2.c:2963)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -82,7 +82,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: mainSort (origin5-bz2.c:2964)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -93,7 +93,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: fallbackSort (origin5-bz2.c:2269)
by 0x........: BZ2_blockSort (origin5-bz2.c:3116)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -104,7 +104,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: fallbackSort (origin5-bz2.c:2275)
by 0x........: BZ2_blockSort (origin5-bz2.c:3116)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
=================================================
./valgrind-new/memcheck/tests/origin5-bz2.stderr.diff-glibc25-x86
=================================================
--- origin5-bz2.stderr.exp-glibc25-x86 2009-07-31 03:15:23.000000000 +1000
+++ origin5-bz2.stderr.out 2009-07-31 03:21:47.000000000 +1000
@@ -28,7 +28,8 @@
at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 4
- at 0x........: BZ2_blockSort (origin5-bz2.c:2820)
+ at 0x........: mainSort (origin5-bz2.c:2820)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
@@ -38,7 +39,8 @@
at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 4
- at 0x........: BZ2_blockSort (origin5-bz2.c:2823)
+ at 0x........: mainSort (origin5-bz2.c:2823)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
@@ -48,7 +50,8 @@
at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 4
- at 0x........: BZ2_blockSort (origin5-bz2.c:2855)
+ at 0x........: mainSort (origin5-bz2.c:2854)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
@@ -58,7 +61,8 @@
at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 4
- at 0x........: BZ2_blockSort (origin5-bz2.c:2859)
+ at 0x........: mainSort (origin5-bz2.c:2858)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
@@ -68,7 +72,8 @@
at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 4
- at 0x........: BZ2_blockSort (origin5-bz2.c:2963)
+ at 0x........: mainSort (origin5-bz2.c:2963)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
@@ -78,7 +83,8 @@
at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 4
- at 0x........: BZ2_blockSort (origin5-bz2.c:2964)
+ at 0x........: mainSort (origin5-bz2.c:2964)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
=================================================
./valgrind-new/memcheck/tests/origin5-bz2.stderr.diff-glibc27-ppc64
=================================================
--- origin5-bz2.stderr.exp-glibc27-ppc64 2009-07-31 03:15:23.000000000 +1000
+++ origin5-bz2.stderr.out 2009-07-31 03:21:47.000000000 +1000
@@ -1,7 +1,7 @@
Conditional jump or move depends on uninitialised value(s)
at 0x........: main (origin5-bz2.c:6481)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
Conditional jump or move depends on uninitialised value(s)
at 0x........: handle_compress (origin5-bz2.c:4686)
@@ -9,85 +9,91 @@
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: handle_compress (origin5-bz2.c:4686)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: handle_compress (origin5-bz2.c:4686)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
- at 0x........: BZ2_blockSort (origin5-bz2.c:2820)
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2820)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
- at 0x........: BZ2_blockSort (origin5-bz2.c:2823)
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2823)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
- at 0x........: BZ2_blockSort (origin5-bz2.c:2854)
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2854)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
- at 0x........: BZ2_blockSort (origin5-bz2.c:2858)
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2858)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
- at 0x........: BZ2_blockSort (origin5-bz2.c:2963)
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2963)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
<truncated beyond 100 lines>
=================================================
./valgrind-new/none/tests/empty-exe.stderr.diff
=================================================
--- empty-exe.stderr.exp 2009-07-31 03:16:12.000000000 +1000
+++ empty-exe.stderr.out 2009-07-31 03:23:10.000000000 +1000
@@ -1,2 +1,2 @@
-
-
+valgrind: wrong ELF executable class (eg. 32-bit instead of 64-bit)
+valgrind: ./empty-exe: bad interpreter (/bin/sh): VG_(strerror): unknown error
=================================================
./valgrind-new/none/tests/shell.stderr.diff
=================================================
--- shell.stderr.exp 2009-07-31 03:16:12.000000000 +1000
+++ shell.stderr.out 2009-07-31 03:23:31.000000000 +1000
@@ -1,8 +1,3 @@
-./shell: ./x86/: is a directory
-./shell: ./shell.vgtest: Permission denied
-execve(0x........(./shell_badinterp), 0x........, 0x........) failed, errno 2
-EXEC FAILED: I can't recover from execve() failing, so I'm dying.
-Add more stringent tests in PRE(sys_execve), or work out how to recover.
-./shell: ./shell_binaryfile: cannot execute binary file
-./shell: ./shell_nosuchfile: No such file or directory
-./shell: shell_nosuchfile: command not found
+valgrind: wrong ELF executable class (eg. 32-bit instead of 64-bit)
+valgrind: wrong ELF executable class (eg. 32-bit instead of 64-bit)
+valgrind: ./shell: bad interpreter (/bin/sh): VG_(strerror): unknown error
=================================================
./valgrind-new/none/tests/shell.stderr.diff-dash
=================================================
--- shell.stderr.exp-dash 2009-07-31 03:16:12.000000000 +1000
+++ shell.stderr.out 2009-07-31 03:23:31.000000000 +1000
@@ -1,8 +1,3 @@
-./shell: 10: ./x86/: Permission denied
-./shell: 13: ./shell.vgtest: Permission denied
-execve(0x........(./shell_badinterp), 0x........, 0x........) failed, errno 2
-EXEC FAILED: I can't recover from execve() failing, so I'm dying.
-Add more stringent tests in PRE(sys_execve), or work out how to recover.
-./shell_binaryfile: 4: Syntax error: ")" unexpected
-./shell: 22: ./shell_nosuchfile: not found
-./shell: 25: shell_nosuchfile: not found
+valgrind: wrong ELF executable class (eg. 32-bit instead of 64-bit)
+valgrind: wrong ELF executable class (eg. 32-bit instead of 64-bit)
+valgrind: ./shell: bad interpreter (/bin/sh): VG_(strerror): unknown error
=================================================
./valgrind-new/none/tests/shell.stdout.diff
=================================================
--- shell.stdout.exp 2009-07-31 03:16:12.000000000 +1000
+++ shell.stdout.out 2009-07-31 03:23:31.000000000 +1000
@@ -1,10 +0,0 @@
-Execute a directory
-Execute a non-executable file
-Execute a script with a bad interpreter name
-Execute a binary file
-Execute a non-existent file
-Execute a non-existent file (2)
-Execute a valid script with a #! line
-Execute a valid script without a #! line
-Execute a valid script with #! but no interpname
-Execute a zero-length file
=================================================
./valgrind-new/none/tests/shell_valid1.stderr.diff
=================================================
--- shell_valid1.stderr.exp 2009-07-31 03:16:12.000000000 +1000
+++ shell_valid1.stderr.out 2009-07-31 03:23:31.000000000 +1000
@@ -0,0 +1,3 @@
+valgrind: wrong ELF executable class (eg. 32-bit instead of 64-bit)
+valgrind: wrong ELF executable class (eg. 32-bit instead of 64-bit)
+valgrind: ./shell_valid1: bad interpreter (/bin/sh): VG_(strerror): unknown error
=================================================
./valgrind-new/none/tests/shell_valid2.stderr.diff
=================================================
--- shell_valid2.stderr.exp 2009-07-31 03:16:12.000000000 +1000
+++ shell_valid2.stderr.out 2009-07-31 03:23:31.000000000 +1000
@@ -0,0 +1,2 @@
+valgrind: wrong ELF executable class (eg. 32-bit instead of 64-bit)
+valgrind: ./shell_valid2: bad interpreter (/bin/sh): VG_(strerror): unknown error
=================================================
./valgrind-new/none/tests/shell_valid3.stderr.diff
=================================================
--- shell_valid3.stderr.exp 2009-07-31 03:16:12.000000000 +1000
+++ shell_valid3.stderr.out 2009-07-31 03:23:31.000000000 +1000
@@ -0,0 +1,2 @@
+valgrind: wrong ELF executable class (eg. 32-bit instead of 64-bit)
+valgrind: ./shell_valid3: bad interpreter (/bin/sh): VG_(strerror): unknown error
=================================================
./valgrind-new/none/tests/shell_zerolength.stderr.diff
=================================================
--- shell_zerolength.stderr.exp 2009-07-31 03:16:12.000000000 +1000
+++ shell_zerolength.stderr.out 2009-07-31 03:23:31.000000000 +1000
@@ -0,0 +1,2 @@
+valgrind: wrong ELF executable class (eg. 32-bit instead of 64-bit)
+valgrind: ./shell_zerolength: bad interpreter (/bin/sh): VG_(strerror): unknown error
=================================================
./valgrind-new/none/tests/shell_zerolength.stderr.diff-dash
=================================================
--- shell_zerolength.stderr.exp-dash 2009-07-31 03:16:12.000000000 +1000
+++ shell_zerolength.stderr.out 2009-07-31 03:23:31.000000000 +1000
@@ -1 +1,2 @@
-Bus error
+valgrind: wrong ELF executable class (eg. 32-bit instead of 64-bit)
+valgrind: ./shell_zerolength: bad interpreter (/bin/sh): VG_(strerror): unknown error
=================================================
./valgrind-old/exp-ptrcheck/tests/supp.stderr.diff
=================================================
--- supp.stderr.exp 2009-07-31 03:00:50.000000000 +1000
+++ supp.stderr.out 2009-07-31 03:14:03.000000000 +1000
@@ -1,7 +1,7 @@
Syscall param write(buf) is non-contiguous
- at 0x........: write (in /...libc...)
- by 0x........: main (supp.c:16)
+ at 0x........: ??? (in /lib32/ld-2.9.so)
+ by 0x........: (below main)
First byte (0x........) is 3 bytes inside a 6-byte block alloc'd
at 0x........: malloc (vg_replace_malloc.c:...)
by 0x........: main (supp.c:12)
=================================================
./valgrind-old/helgrind/tests/tc06_two_races_xml.stderr.diff
=================================================
--- tc06_two_races_xml.stderr.exp 2009-07-31 03:00:41.000000000 +1000
+++ tc06_two_races_xml.stderr.out 2009-07-31 03:11:31.000000000 +1000
@@ -43,16 +43,6 @@
<frame>
<ip>0x........</ip>
<obj>...</obj>
- <fn>do_clone</fn>
- </frame>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
- <fn>pthread_create@@GLIBC_2.2.5</fn>
- </frame>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
<fn>pthread_create_WRK</fn>
<dir>...</dir>
<file>hg_intercepts.c</file>
=================================================
./valgrind-old/memcheck/tests/origin5-bz2.stderr.diff-glibc25-amd64
=================================================
--- origin5-bz2.stderr.exp-glibc25-amd64 2009-07-31 03:01:45.000000000 +1000
+++ origin5-bz2.stderr.out 2009-07-31 03:08:59.000000000 +1000
@@ -11,7 +11,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: handle_compress (origin5-bz2.c:4686)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
@@ -19,7 +19,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: handle_compress (origin5-bz2.c:4686)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
@@ -27,7 +27,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: mainSort (origin5-bz2.c:2820)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -38,7 +38,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: mainSort (origin5-bz2.c:2823)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -49,7 +49,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: mainSort (origin5-bz2.c:2854)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -60,7 +60,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: mainSort (origin5-bz2.c:2858)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -71,7 +71,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: mainSort (origin5-bz2.c:2963)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -82,7 +82,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: mainSort (origin5-bz2.c:2964)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -93,7 +93,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: fallbackSort (origin5-bz2.c:2269)
by 0x........: BZ2_blockSort (origin5-bz2.c:3116)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -104,7 +104,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: fallbackSort (origin5-bz2.c:2275)
by 0x........: BZ2_blockSort (origin5-bz2.c:3116)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
=================================================
./valgrind-old/memcheck/tests/origin5-bz2.stderr.diff-glibc25-x86
=================================================
--- origin5-bz2.stderr.exp-glibc25-x86 2009-07-31 03:01:45.000000000 +1000
+++ origin5-bz2.stderr.out 2009-07-31 03:08:59.000000000 +1000
@@ -28,7 +28,8 @@
at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 4
- at 0x........: BZ2_blockSort (origin5-bz2.c:2820)
+ at 0x........: mainSort (origin5-bz2.c:2820)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
@@ -38,7 +39,8 @@
at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 4
- at 0x........: BZ2_blockSort (origin5-bz2.c:2823)
+ at 0x........: mainSort (origin5-bz2.c:2823)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
@@ -48,7 +50,8 @@
at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 4
- at 0x........: BZ2_blockSort (origin5-bz2.c:2855)
+ at 0x........: mainSort (origin5-bz2.c:2854)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
@@ -58,7 +61,8 @@
at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 4
- at 0x........: BZ2_blockSort (origin5-bz2.c:2859)
+ at 0x........: mainSort (origin5-bz2.c:2858)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
@@ -68,7 +72,8 @@
at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 4
- at 0x........: BZ2_blockSort (origin5-bz2.c:2963)
+ at 0x........: mainSort (origin5-bz2.c:2963)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
@@ -78,7 +83,8 @@
at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 4
- at 0x........: BZ2_blockSort (origin5-bz2.c:2964)
+ at 0x........: mainSort (origin5-bz2.c:2964)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
=================================================
./valgrind-old/memcheck/tests/origin5-bz2.stderr.diff-glibc27-ppc64
=================================================
--- origin5-bz2.stderr.exp-glibc27-ppc64 2009-07-31 03:01:45.000000000 +1000
+++ origin5-bz2.stderr.out 2009-07-31 03:08:59.000000000 +1000
@@ -1,7 +1,7 @@
Conditional jump or move depends on uninitialised value(s)
at 0x........: main (origin5-bz2.c:6481)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
Conditional jump or move depends on uninitialised value(s)
at 0x........: handle_compress (origin5-bz2.c:4686)
@@ -9,85 +9,91 @@
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: handle_compress (origin5-bz2.c:4686)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: handle_compress (origin5-bz2.c:4686)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
- at 0x........: BZ2_blockSort (origin5-bz2.c:2820)
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2820)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
- at 0x........: BZ2_blockSort (origin5-bz2.c:2823)
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2823)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
- at 0x........: BZ2_blockSort (origin5-bz2.c:2854)
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2854)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
- at 0x........: BZ2_blockSort (origin5-bz2.c:2858)
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2858)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
- at 0x........: BZ2_blockSort (origin5-bz2.c:2963)
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2963)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
<truncated beyond 100 lines>
=================================================
./valgrind-old/none/tests/empty-exe.stderr.diff
=================================================
--- empty-exe.stderr.exp 2009-07-31 03:02:40.000000000 +1000
+++ empty-exe.stderr.out 2009-07-31 03:10:21.000000000 +1000
@@ -1,2 +1,2 @@
-
-
+valgrind: wrong ELF executable class (eg. 32-bit instead of 64-bit)
+valgrind: ./empty-exe: bad interpreter (/bin/sh): VG_(strerror): unknown error
=================================================
./valgrind-old/none/tests/shell.stderr.diff
=================================================
--- shell.stderr.exp 2009-07-31 03:02:40.000000000 +1000
+++ shell.stderr.out 2009-07-31 03:10:42.000000000 +1000
@@ -1,8 +1,3 @@
-./shell: ./x86/: is a directory
-./shell: ./shell.vgtest: Permission denied
-execve(0x........(./shell_badinterp), 0x........, 0x........) failed, errno 2
-EXEC FAILED: I can't recover from execve() failing, so I'm dying.
-Add more stringent tests in PRE(sys_execve), or work out how to recover.
-./shell: ./shell_binaryfile: cannot execute binary file
-./shell: ./shell_nosuchfile: No such file or directory
-./shell: shell_nosuchfile: command not found
+valgrind: wrong ELF executable class (eg. 32-bit instead of 64-bit)
+valgrind: wrong ELF executable class (eg. 32-bit instead of 64-bit)
+valgrind: ./shell: bad interpreter (/bin/sh): VG_(strerror): unknown error
=================================================
./valgrind-old/none/tests/shell.stderr.diff-dash
=================================================
--- shell.stderr.exp-dash 2009-07-31 03:02:40.000000000 +1000
+++ shell.stderr.out 2009-07-31 03:10:42.000000000 +1000
@@ -1,8 +1,3 @@
-./shell: 10: ./x86/: Permission denied
-./shell: 13: ./shell.vgtest: Permission denied
-execve(0x........(./shell_badinterp), 0x........, 0x........) failed, errno 2
-EXEC FAILED: I can't recover from execve() failing, so I'm dying.
-Add more stringent tests in PRE(sys_execve), or work out how to recover.
-./shell_binaryfile: 4: Syntax error: ")" unexpected
-./shell: 22: ./shell_nosuchfile: not found
-./shell: 25: shell_nosuchfile: not found
+valgrind: wrong ELF executable class (eg. 32-bit instead of 64-bit)
+valgrind: wrong ELF executable class (eg. 32-bit instead of 64-bit)
+valgrind: ./shell: bad interpreter (/bin/sh): VG_(strerror): unknown error
=================================================
./valgrind-old/none/tests/shell.stdout.diff
=================================================
--- shell.stdout.exp 2009-07-31 03:02:40.000000000 +1000
+++ shell.stdout.out 2009-07-31 03:10:42.000000000 +1000
@@ -1,10 +0,0 @@
-Execute a directory
-Execute a non-executable file
-Execute a script with a bad interpreter name
-Execute a binary file
-Execute a non-existent file
-Execute a non-existent file (2)
-Execute a valid script with a #! line
-Execute a valid script without a #! line
-Execute a valid script with #! but no interpname
-Execute a zero-length file
=================================================
./valgrind-old/none/tests/shell_valid1.stderr.diff
=================================================
--- shell_valid1.stderr.exp 2009-07-31 03:02:40.000000000 +1000
+++ shell_valid1.stderr.out 2009-07-31 03:10:42.000000000 +1000
@@ -0,0 +1,3 @@
+valgrind: wrong ELF executable class (eg. 32-bit instead of 64-bit)
+valgrind: wrong ELF executable class (eg. 32-bit instead of 64-bit)
+valgrind: ./shell_valid1: bad interpreter (/bin/sh): VG_(strerror): unknown error
=================================================
./valgrind-old/none/tests/shell_valid2.stderr.diff
=================================================
--- shell_valid2.stderr.exp 2009-07-31 03:02:40.000000000 +1000
+++ shell_valid2.stderr.out 2009-07-31 03:10:42.000000000 +1000
@@ -0,0 +1,2 @@
+valgrind: wrong ELF executable class (eg. 32-bit instead of 64-bit)
+valgrind: ./shell_valid2: bad interpreter (/bin/sh): VG_(strerror): unknown error
=================================================
./valgrind-old/none/tests/shell_valid3.stderr.diff
=================================================
--- shell_valid3.stderr.exp 2009-07-31 03:02:40.000000000 +1000
+++ shell_valid3.stderr.out 2009-07-31 03:10:42.000000000 +1000
@@ -0,0 +1,2 @@
+valgrind: wrong ELF executable class (eg. 32-bit instead of 64-bit)
+valgrind: ./shell_valid3: bad interpreter (/bin/sh): VG_(strerror): unknown error
=================================================
./valgrind-old/none/tests/shell_zerolength.stderr.diff
=================================================
--- shell_zerolength.stderr.exp 2009-07-31 03:02:40.000000000 +1000
+++ shell_zerolength.stderr.out 2009-07-31 03:10:42.000000000 +1000
@@ -0,0 +1,2 @@
+valgrind: wrong ELF executable class (eg. 32-bit instead of 64-bit)
+valgrind: ./shell_zerolength: bad interpreter (/bin/sh): VG_(strerror): unknown error
=================================================
./valgrind-old/none/tests/shell_zerolength.stderr.diff-dash
=================================================
--- shell_zerolength.stderr.exp-dash 2009-07-31 03:02:40.000000000 +1000
+++ shell_zerolength.stderr.out 2009-07-31 03:10:42.000000000 +1000
@@ -1 +1,2 @@
-Bus error
+valgrind: wrong ELF executable class (eg. 32-bit instead of 64-bit)
+valgrind: ./shell_zerolength: bad interpreter (/bin/sh): VG_(strerror): unknown error
|
|
From: Nicholas N. <n.n...@gm...> - 2009-07-30 16:30:45
|
Nightly build on ocean ( Ubuntu 9.04, x86_64 )
Started at 2009-07-31 02:00:01 EST
Ended at 2009-07-31 02:30:21 EST
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
== 526 tests, 1 stderr failure, 0 stdout failures, 0 post failures ==
helgrind/tests/tc06_two_races_xml (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
== 525 tests, 1 stderr failure, 0 stdout failures, 0 post failures ==
helgrind/tests/tc06_two_races_xml (stderr)
=================================================
== Difference between 24 hours ago and now ==
=================================================
*** old.short Fri Jul 31 02:13:21 2009
--- new.short Fri Jul 31 02:30:21 2009
***************
*** 8,10 ****
! == 525 tests, 1 stderr failure, 0 stdout failures, 0 post failures ==
helgrind/tests/tc06_two_races_xml (stderr)
--- 8,10 ----
! == 526 tests, 1 stderr failure, 0 stdout failures, 0 post failures ==
helgrind/tests/tc06_two_races_xml (stderr)
=================================================
./valgrind-new/helgrind/tests/tc06_two_races_xml.stderr.diff
=================================================
--- tc06_two_races_xml.stderr.exp 2009-07-31 02:13:52.000000000 +1000
+++ tc06_two_races_xml.stderr.out 2009-07-31 02:27:59.000000000 +1000
@@ -43,11 +43,6 @@
<frame>
<ip>0x........</ip>
<obj>...</obj>
- <fn>do_clone</fn>
- </frame>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
<fn>pthread_create@@GLIBC_2.2.5</fn>
</frame>
<frame>
=================================================
./valgrind-old/helgrind/tests/tc06_two_races_xml.stderr.diff
=================================================
--- tc06_two_races_xml.stderr.exp 2009-07-31 02:00:35.000000000 +1000
+++ tc06_two_races_xml.stderr.out 2009-07-31 02:11:00.000000000 +1000
@@ -43,11 +43,6 @@
<frame>
<ip>0x........</ip>
<obj>...</obj>
- <fn>do_clone</fn>
- </frame>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
<fn>pthread_create@@GLIBC_2.2.5</fn>
</frame>
<frame>
|
|
From: Rich C. <Ric...@me...> - 2009-07-30 15:23:03
|
Nightly build on macbook ( Darwin 9.6.0 i386 )
Started at 2009-07-30 07:25:10 CDT
Ended at 2009-07-30 07:47:51 CDT
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
== 380 tests, 6 stderr failures, 1 stdout failure, 0 post failures ==
memcheck/tests/origin5-bz2 (stderr)
memcheck/tests/varinfo3 (stderr)
memcheck/tests/varinfo5 (stderr)
memcheck/tests/vcpu_fnfns (stdout)
none/tests/async-sigs (stderr)
none/tests/faultstatus (stderr)
none/tests/pth_blockedsig (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
== 379 tests, 6 stderr failures, 1 stdout failure, 0 post failures ==
memcheck/tests/origin5-bz2 (stderr)
memcheck/tests/varinfo3 (stderr)
memcheck/tests/varinfo5 (stderr)
memcheck/tests/vcpu_fnfns (stdout)
none/tests/async-sigs (stderr)
none/tests/faultstatus (stderr)
none/tests/pth_blockedsig (stderr)
=================================================
== Difference between 24 hours ago and now ==
=================================================
*** old.short 2009-07-30 07:35:57.000000000 -0500
--- new.short 2009-07-30 07:47:51.000000000 -0500
***************
*** 8,10 ****
! == 379 tests, 6 stderr failures, 1 stdout failure, 0 post failures ==
memcheck/tests/origin5-bz2 (stderr)
--- 8,10 ----
! == 380 tests, 6 stderr failures, 1 stdout failure, 0 post failures ==
memcheck/tests/origin5-bz2 (stderr)
=================================================
./valgrind-new/memcheck/tests/origin5-bz2.stderr.diff-glibc25-amd64
=================================================
--- origin5-bz2.stderr.exp-glibc25-amd64 2009-07-30 07:36:37.000000000 -0500
+++ origin5-bz2.stderr.out 2009-07-30 07:42:43.000000000 -0500
@@ -11,7 +11,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: handle_compress (origin5-bz2.c:4686)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
@@ -19,7 +19,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: handle_compress (origin5-bz2.c:4686)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
@@ -27,7 +27,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: mainSort (origin5-bz2.c:2820)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -38,7 +38,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: mainSort (origin5-bz2.c:2823)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -49,8 +49,8 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
- at 0x........: mainSort (origin5-bz2.c:2854)
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2855)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
@@ -60,8 +60,8 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
- at 0x........: mainSort (origin5-bz2.c:2858)
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2859)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
@@ -71,7 +71,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: mainSort (origin5-bz2.c:2963)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -82,7 +82,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: mainSort (origin5-bz2.c:2964)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -93,7 +93,18 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2964)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
+ by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
+ by 0x........: handle_compress (origin5-bz2.c:4753)
+ by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
+ by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
+ by 0x........: main (origin5-bz2.c:6484)
+ Uninitialised value was created by a client request
+ at 0x........: main (origin5-bz2.c:6479)
+
+Use of uninitialised value of size 4
at 0x........: fallbackSort (origin5-bz2.c:2269)
by 0x........: BZ2_blockSort (origin5-bz2.c:3116)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -104,7 +115,7 @@
Uninitialised value was created by a client request
<truncated beyond 100 lines>
=================================================
./valgrind-new/memcheck/tests/origin5-bz2.stderr.diff-glibc25-x86
=================================================
--- origin5-bz2.stderr.exp-glibc25-x86 2009-07-30 07:36:40.000000000 -0500
+++ origin5-bz2.stderr.out 2009-07-30 07:42:43.000000000 -0500
@@ -28,7 +28,8 @@
at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 4
- at 0x........: BZ2_blockSort (origin5-bz2.c:2820)
+ at 0x........: mainSort (origin5-bz2.c:2820)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
@@ -38,7 +39,8 @@
at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 4
- at 0x........: BZ2_blockSort (origin5-bz2.c:2823)
+ at 0x........: mainSort (origin5-bz2.c:2823)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
@@ -48,7 +50,8 @@
at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 4
- at 0x........: BZ2_blockSort (origin5-bz2.c:2855)
+ at 0x........: mainSort (origin5-bz2.c:2855)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
@@ -58,7 +61,8 @@
at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 4
- at 0x........: BZ2_blockSort (origin5-bz2.c:2859)
+ at 0x........: mainSort (origin5-bz2.c:2859)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
@@ -68,7 +72,8 @@
at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 4
- at 0x........: BZ2_blockSort (origin5-bz2.c:2963)
+ at 0x........: mainSort (origin5-bz2.c:2963)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
@@ -78,7 +83,19 @@
at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 4
- at 0x........: BZ2_blockSort (origin5-bz2.c:2964)
+ at 0x........: mainSort (origin5-bz2.c:2964)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
+ by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
+ by 0x........: handle_compress (origin5-bz2.c:4753)
+ by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
+ by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
+ by 0x........: main (origin5-bz2.c:6484)
+ Uninitialised value was created by a client request
+ at 0x........: main (origin5-bz2.c:6479)
+
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2964)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
=================================================
./valgrind-new/memcheck/tests/origin5-bz2.stderr.diff-glibc27-ppc64
=================================================
--- origin5-bz2.stderr.exp-glibc27-ppc64 2009-07-30 07:36:37.000000000 -0500
+++ origin5-bz2.stderr.out 2009-07-30 07:42:43.000000000 -0500
@@ -1,7 +1,7 @@
Conditional jump or move depends on uninitialised value(s)
at 0x........: main (origin5-bz2.c:6481)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
Conditional jump or move depends on uninitialised value(s)
at 0x........: handle_compress (origin5-bz2.c:4686)
@@ -9,85 +9,102 @@
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: handle_compress (origin5-bz2.c:4686)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: handle_compress (origin5-bz2.c:4686)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
- at 0x........: BZ2_blockSort (origin5-bz2.c:2820)
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2820)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
- at 0x........: BZ2_blockSort (origin5-bz2.c:2823)
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2823)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
- at 0x........: BZ2_blockSort (origin5-bz2.c:2854)
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2855)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
- at 0x........: BZ2_blockSort (origin5-bz2.c:2858)
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2859)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
- at 0x........: BZ2_blockSort (origin5-bz2.c:2963)
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2963)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
<truncated beyond 100 lines>
=================================================
./valgrind-new/memcheck/tests/varinfo3.stderr.diff
=================================================
--- varinfo3.stderr.exp 2009-07-30 07:36:38.000000000 -0500
+++ varinfo3.stderr.out 2009-07-30 07:43:25.000000000 -0500
@@ -31,7 +31,7 @@
by 0x........: bar (varinfo3.c:42)
by 0x........: foo (varinfo3.c:58)
by 0x........: main (varinfo3.c:66)
- Address 0x........ is 5 bytes inside data symbol "static_local_def.XXXX"
+ Address 0x........ is in the Data segment of ./varinfo3
Uninitialised byte(s) found during client check request
at 0x........: croak (varinfo3.c:28)
@@ -46,7 +46,7 @@
by 0x........: bar (varinfo3.c:44)
by 0x........: foo (varinfo3.c:58)
by 0x........: main (varinfo3.c:66)
- Address 0x........ is 7 bytes inside data symbol "static_local_undef.XXXX"
+ Address 0x........ is in the Data segment of ./varinfo3
Uninitialised byte(s) found during client check request
at 0x........: croak (varinfo3.c:28)
=================================================
./valgrind-new/memcheck/tests/varinfo5.stderr.diff
=================================================
--- varinfo5.stderr.exp 2009-07-30 07:36:39.000000000 -0500
+++ varinfo5.stderr.out 2009-07-30 07:43:26.000000000 -0500
@@ -119,7 +119,7 @@
by 0x........: varinfo3_main (varinfo5so.c:118)
by 0x........: varinfo5_main (varinfo5so.c:156)
by 0x........: main (varinfo5.c:5)
- Address 0x........ is 5 bytes inside data symbol "static_local_def.XXXX"
+ Address 0x........ is in the Data segment of /Users/coe/src/vg/nightly/valgrind-new/memcheck/tests/varinfo5so.so
Uninitialised byte(s) found during client check request
at 0x........: croak (varinfo5so.c:29)
@@ -138,7 +138,7 @@
by 0x........: varinfo3_main (varinfo5so.c:118)
by 0x........: varinfo5_main (varinfo5so.c:156)
by 0x........: main (varinfo5.c:5)
- Address 0x........ is 7 bytes inside data symbol "static_local_undef.XXXX"
+ Address 0x........ is in the Data segment of /Users/coe/src/vg/nightly/valgrind-new/memcheck/tests/varinfo5so.so
Uninitialised byte(s) found during client check request
at 0x........: croak (varinfo5so.c:29)
=================================================
./valgrind-new/memcheck/tests/vcpu_fnfns.stdout.diff
=================================================
--- vcpu_fnfns.stdout.exp 2009-07-30 07:36:37.000000000 -0500
+++ vcpu_fnfns.stdout.out 2009-07-30 07:43:32.000000000 -0500
@@ -91,16 +91,16 @@
ceilD(-1.2000000008000e+00) = -1.0000000000000e+00
ceilD(-1.1000000009000e+00) = -1.0000000000000e+00
ceilD(-1.0000000010000e+00) = -1.0000000000000e+00
- ceilD(-9.0000000110000e-01) = -0.0000000000000e+00
- ceilD(-8.0000000120000e-01) = -0.0000000000000e+00
- ceilD(-7.0000000130000e-01) = -0.0000000000000e+00
- ceilD(-6.0000000140000e-01) = -0.0000000000000e+00
- ceilD(-5.0000000150000e-01) = -0.0000000000000e+00
- ceilD(-4.0000000160000e-01) = -0.0000000000000e+00
- ceilD(-3.0000000170000e-01) = -0.0000000000000e+00
- ceilD(-2.0000000180000e-01) = -0.0000000000000e+00
- ceilD(-1.0000000190000e-01) = -0.0000000000000e+00
- ceilD(-1.9999992495467e-09) = -0.0000000000000e+00
+ ceilD(-9.0000000110000e-01) = +0.0000000000000e+00
+ ceilD(-8.0000000120000e-01) = +0.0000000000000e+00
+ ceilD(-7.0000000130000e-01) = +0.0000000000000e+00
+ ceilD(-6.0000000140000e-01) = +0.0000000000000e+00
+ ceilD(-5.0000000150000e-01) = +0.0000000000000e+00
+ ceilD(-4.0000000160000e-01) = +0.0000000000000e+00
+ ceilD(-3.0000000170000e-01) = +0.0000000000000e+00
+ ceilD(-2.0000000180000e-01) = +0.0000000000000e+00
+ ceilD(-1.0000000190000e-01) = +0.0000000000000e+00
+ ceilD(-1.9999992495467e-09) = +0.0000000000000e+00
ceilD(+9.9999997900001e-02) = +1.0000000000000e+00
ceilD(+1.9999999780000e-01) = +1.0000000000000e+00
ceilD(+2.9999999770000e-01) = +1.0000000000000e+00
@@ -132,16 +132,16 @@
ceilF( -1.2008e+00) = -1.0000e+00
ceilF( -1.1009e+00) = -1.0000e+00
ceilF( -1.0010e+00) = -1.0000e+00
- ceilF( -9.0110e-01) = -0.0000e+00
- ceilF( -8.0120e-01) = -0.0000e+00
- ceilF( -7.0130e-01) = -0.0000e+00
- ceilF( -6.0140e-01) = -0.0000e+00
- ceilF( -5.0150e-01) = -0.0000e+00
- ceilF( -4.0160e-01) = -0.0000e+00
- ceilF( -3.0170e-01) = -0.0000e+00
- ceilF( -2.0180e-01) = -0.0000e+00
- ceilF( -1.0190e-01) = -0.0000e+00
- ceilF( -1.9999e-03) = -0.0000e+00
+ ceilF( -9.0110e-01) = +0.0000e+00
+ ceilF( -8.0120e-01) = +0.0000e+00
+ ceilF( -7.0130e-01) = +0.0000e+00
+ ceilF( -6.0140e-01) = +0.0000e+00
+ ceilF( -5.0150e-01) = +0.0000e+00
+ ceilF( -4.0160e-01) = +0.0000e+00
+ ceilF( -3.0170e-01) = +0.0000e+00
+ ceilF( -2.0180e-01) = +0.0000e+00
+ ceilF( -1.0190e-01) = +0.0000e+00
+ ceilF( -1.9999e-03) = +0.0000e+00
ceilF( +9.7900e-02) = +1.0000e+00
ceilF( +1.9780e-01) = +1.0000e+00
ceilF( +2.9770e-01) = +1.0000e+00
@@ -305,7 +305,7 @@
cosF( -3.0170e-01) = +9.5483e-01
cosF( -2.0180e-01) = +9.7971e-01
cosF( -1.0190e-01) = +9.9481e-01
- cosF( -1.9999e-03) = +1.0000e-00
+ cosF( -1.9999e-03) = +1.0000e+00
cosF( +9.7900e-02) = +9.9521e-01
cosF( +1.9780e-01) = +9.8050e-01
cosF( +2.9770e-01) = +9.5601e-01
@@ -536,7 +536,7 @@
logD(+9.9999999900000e-02) = -2.3025850939940e+00
logD(+1.9999999980000e-01) = -1.6094379134341e+00
logD(+2.9999999970000e-01) = -1.2039728053259e+00
- logD(+3.9999999960000e-01) = -9.1629073287415e-01
+ logD(+3.9999999960000e-01) = -9.1629073287416e-01
logD(+4.9999999950000e-01) = -6.9314718155995e-01
logD(+5.9999999940000e-01) = -5.1082562476599e-01
logD(+6.9999999930000e-01) = -3.5667494493873e-01
@@ -617,7 +617,7 @@
log10F( +1.8981e+00) = +2.7832e-01
log10F( +1.9980e+00) = +3.0060e-01
asinD(-1.0000000000000e+00) = -1.5707963267949e+00
- asinD(-9.0000000010000e-01) = -1.1197695152281e+00
+ asinD(-9.0000000010000e-01) = -1.1197695152280e+00
asinD(-8.0000000020000e-01) = -9.2729521833495e-01
asinD(-7.0000000030000e-01) = -7.7539749703084e-01
asinD(-6.0000000040000e-01) = -6.4350110929328e-01
=================================================
./valgrind-new/memcheck/tests/vcpu_fnfns.stdout.diff-glibc28-amd64
=================================================
--- vcpu_fnfns.stdout.exp-glibc28-amd64 2009-07-30 07:36:38.000000000 -0500
+++ vcpu_fnfns.stdout.out 2009-07-30 07:43:32.000000000 -0500
@@ -91,16 +91,16 @@
ceilD(-1.2000000008000e+00) = -1.0000000000000e+00
ceilD(-1.1000000009000e+00) = -1.0000000000000e+00
ceilD(-1.0000000010000e+00) = -1.0000000000000e+00
- ceilD(-9.0000000110000e-01) = -0.0000000000000e+00
- ceilD(-8.0000000120000e-01) = -0.0000000000000e+00
- ceilD(-7.0000000130000e-01) = -0.0000000000000e+00
- ceilD(-6.0000000140000e-01) = -0.0000000000000e+00
- ceilD(-5.0000000150000e-01) = -0.0000000000000e+00
- ceilD(-4.0000000160000e-01) = -0.0000000000000e+00
- ceilD(-3.0000000170000e-01) = -0.0000000000000e+00
- ceilD(-2.0000000180000e-01) = -0.0000000000000e+00
- ceilD(-1.0000000190000e-01) = -0.0000000000000e+00
- ceilD(-1.9999992495467e-09) = -0.0000000000000e+00
+ ceilD(-9.0000000110000e-01) = +0.0000000000000e+00
+ ceilD(-8.0000000120000e-01) = +0.0000000000000e+00
+ ceilD(-7.0000000130000e-01) = +0.0000000000000e+00
+ ceilD(-6.0000000140000e-01) = +0.0000000000000e+00
+ ceilD(-5.0000000150000e-01) = +0.0000000000000e+00
+ ceilD(-4.0000000160000e-01) = +0.0000000000000e+00
+ ceilD(-3.0000000170000e-01) = +0.0000000000000e+00
+ ceilD(-2.0000000180000e-01) = +0.0000000000000e+00
+ ceilD(-1.0000000190000e-01) = +0.0000000000000e+00
+ ceilD(-1.9999992495467e-09) = +0.0000000000000e+00
ceilD(+9.9999997900001e-02) = +1.0000000000000e+00
ceilD(+1.9999999780000e-01) = +1.0000000000000e+00
ceilD(+2.9999999770000e-01) = +1.0000000000000e+00
@@ -132,16 +132,16 @@
ceilF( -1.2008e+00) = -1.0000e+00
ceilF( -1.1009e+00) = -1.0000e+00
ceilF( -1.0010e+00) = -1.0000e+00
- ceilF( -9.0110e-01) = -0.0000e+00
- ceilF( -8.0120e-01) = -0.0000e+00
- ceilF( -7.0130e-01) = -0.0000e+00
- ceilF( -6.0140e-01) = -0.0000e+00
- ceilF( -5.0150e-01) = -0.0000e+00
- ceilF( -4.0160e-01) = -0.0000e+00
- ceilF( -3.0170e-01) = -0.0000e+00
- ceilF( -2.0180e-01) = -0.0000e+00
- ceilF( -1.0190e-01) = -0.0000e+00
- ceilF( -1.9999e-03) = -0.0000e+00
+ ceilF( -9.0110e-01) = +0.0000e+00
+ ceilF( -8.0120e-01) = +0.0000e+00
+ ceilF( -7.0130e-01) = +0.0000e+00
+ ceilF( -6.0140e-01) = +0.0000e+00
+ ceilF( -5.0150e-01) = +0.0000e+00
+ ceilF( -4.0160e-01) = +0.0000e+00
+ ceilF( -3.0170e-01) = +0.0000e+00
+ ceilF( -2.0180e-01) = +0.0000e+00
+ ceilF( -1.0190e-01) = +0.0000e+00
+ ceilF( -1.9999e-03) = +0.0000e+00
ceilF( +9.7900e-02) = +1.0000e+00
ceilF( +1.9780e-01) = +1.0000e+00
ceilF( +2.9770e-01) = +1.0000e+00
@@ -536,7 +536,7 @@
logD(+9.9999999900000e-02) = -2.3025850939940e+00
logD(+1.9999999980000e-01) = -1.6094379134341e+00
logD(+2.9999999970000e-01) = -1.2039728053259e+00
- logD(+3.9999999960000e-01) = -9.1629073287415e-01
+ logD(+3.9999999960000e-01) = -9.1629073287416e-01
logD(+4.9999999950000e-01) = -6.9314718155995e-01
logD(+5.9999999940000e-01) = -5.1082562476599e-01
logD(+6.9999999930000e-01) = -3.5667494493873e-01
@@ -617,7 +617,7 @@
log10F( +1.8981e+00) = +2.7832e-01
log10F( +1.9980e+00) = +3.0060e-01
asinD(-1.0000000000000e+00) = -1.5707963267949e+00
- asinD(-9.0000000010000e-01) = -1.1197695152281e+00
+ asinD(-9.0000000010000e-01) = -1.1197695152280e+00
asinD(-8.0000000020000e-01) = -9.2729521833495e-01
asinD(-7.0000000030000e-01) = -7.7539749703084e-01
asinD(-6.0000000040000e-01) = -6.4350110929328e-01
=================================================
./valgrind-new/none/tests/async-sigs.stderr.diff
=================================================
--- async-sigs.stderr.exp 2009-07-30 07:36:58.000000000 -0500
+++ async-sigs.stderr.out 2009-07-30 07:44:38.000000000 -0500
@@ -1,8 +1,30 @@
-testing: blocking=0 caught=11 fatal=7... PASSED
+testing: blocking=0 caught=11 fatal=10...
+Process terminating with default action of signal 10 (SIGBUS)
+ Non-existent physical address at address 0x........
+ at 0x........: test (async-sigs.c:94)
+ by 0x........: main (async-sigs.c:129)
+PASSED
testing: blocking=0 caught=11 fatal=1... PASSED
-testing: blocking=0 caught=10 fatal=7... PASSED
-testing: blocking=0 caught=10 fatal=1... PASSED
-testing: blocking=1 caught=11 fatal=7... PASSED
+testing: blocking=0 caught=30 fatal=10...
+Process terminating with default action of signal 10 (SIGBUS)
+ Non-existent physical address at address 0x........
+ at 0x........: test (async-sigs.c:94)
+ by 0x........: main (async-sigs.c:131)
+PASSED
+testing: blocking=0 caught=30 fatal=1... PASSED
+testing: blocking=1 caught=11 fatal=10...
+Process terminating with default action of signal 10 (SIGBUS)
+ Non-existent physical address at address 0x........
+ at 0x........: __sigsuspend (in /...libc...)
+ by 0x........: test (async-sigs.c:95)
+ by 0x........: main (async-sigs.c:133)
+PASSED
testing: blocking=1 caught=11 fatal=1... PASSED
-testing: blocking=1 caught=10 fatal=7... PASSED
-testing: blocking=1 caught=10 fatal=1... PASSED
+testing: blocking=1 caught=30 fatal=10...
+Process terminating with default action of signal 10 (SIGBUS)
+ Non-existent physical address at address 0x........
+ at 0x........: __sigsuspend (in /...libc...)
+ by 0x........: test (async-sigs.c:95)
+ by 0x........: main (async-sigs.c:135)
+PASSED
+testing: blocking=1 caught=30 fatal=1... PASSED
=================================================
./valgrind-new/none/tests/faultstatus.stderr.diff
=================================================
--- faultstatus.stderr.exp 2009-07-30 07:36:59.000000000 -0500
+++ faultstatus.stderr.out 2009-07-30 07:44:42.000000000 -0500
@@ -1,6 +1,6 @@
-Test 1: PASS
-Test 2: PASS
-Test 3: PASS
-Test 4: PASS
+Test 1: FAIL: expected signal 11, not 10
+Test 2: FAIL: expected signal 11, not 10
+Test 3: FAIL: no fault, or handler returned
+Test 4: FAIL: expected si_code==7, not 0
=================================================
./valgrind-new/none/tests/pth_blockedsig.stderr.diff
=================================================
--- pth_blockedsig.stderr.exp 2009-07-30 07:36:58.000000000 -0500
+++ pth_blockedsig.stderr.out 2009-07-30 07:45:46.000000000 -0500
@@ -1,2 +1,4 @@
+UNKNOWN __pthread_sigmask is unsupported. This warning will not be repeated.
+SHOULD NOT BE HERE (SIGUSR1)!!!!
=================================================
./valgrind-old/memcheck/tests/origin5-bz2.stderr.diff-glibc25-amd64
=================================================
--- origin5-bz2.stderr.exp-glibc25-amd64 2009-07-30 07:25:43.000000000 -0500
+++ origin5-bz2.stderr.out 2009-07-30 07:30:47.000000000 -0500
@@ -11,7 +11,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: handle_compress (origin5-bz2.c:4686)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
@@ -19,7 +19,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: handle_compress (origin5-bz2.c:4686)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
@@ -27,7 +27,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: mainSort (origin5-bz2.c:2820)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -38,7 +38,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: mainSort (origin5-bz2.c:2823)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -49,8 +49,8 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
- at 0x........: mainSort (origin5-bz2.c:2854)
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2855)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
@@ -60,8 +60,8 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
- at 0x........: mainSort (origin5-bz2.c:2858)
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2859)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
@@ -71,7 +71,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: mainSort (origin5-bz2.c:2963)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -82,7 +82,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: mainSort (origin5-bz2.c:2964)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -93,7 +93,18 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2964)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
+ by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
+ by 0x........: handle_compress (origin5-bz2.c:4753)
+ by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
+ by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
+ by 0x........: main (origin5-bz2.c:6484)
+ Uninitialised value was created by a client request
+ at 0x........: main (origin5-bz2.c:6479)
+
+Use of uninitialised value of size 4
at 0x........: fallbackSort (origin5-bz2.c:2269)
by 0x........: BZ2_blockSort (origin5-bz2.c:3116)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -104,7 +115,7 @@
Uninitialised value was created by a client request
<truncated beyond 100 lines>
=================================================
./valgrind-old/memcheck/tests/origin5-bz2.stderr.diff-glibc25-x86
=================================================
--- origin5-bz2.stderr.exp-glibc25-x86 2009-07-30 07:25:46.000000000 -0500
+++ origin5-bz2.stderr.out 2009-07-30 07:30:47.000000000 -0500
@@ -28,7 +28,8 @@
at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 4
- at 0x........: BZ2_blockSort (origin5-bz2.c:2820)
+ at 0x........: mainSort (origin5-bz2.c:2820)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
@@ -38,7 +39,8 @@
at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 4
- at 0x........: BZ2_blockSort (origin5-bz2.c:2823)
+ at 0x........: mainSort (origin5-bz2.c:2823)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
@@ -48,7 +50,8 @@
at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 4
- at 0x........: BZ2_blockSort (origin5-bz2.c:2855)
+ at 0x........: mainSort (origin5-bz2.c:2855)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
@@ -58,7 +61,8 @@
at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 4
- at 0x........: BZ2_blockSort (origin5-bz2.c:2859)
+ at 0x........: mainSort (origin5-bz2.c:2859)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
@@ -68,7 +72,8 @@
at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 4
- at 0x........: BZ2_blockSort (origin5-bz2.c:2963)
+ at 0x........: mainSort (origin5-bz2.c:2963)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
@@ -78,7 +83,19 @@
at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 4
- at 0x........: BZ2_blockSort (origin5-bz2.c:2964)
+ at 0x........: mainSort (origin5-bz2.c:2964)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
+ by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
+ by 0x........: handle_compress (origin5-bz2.c:4753)
+ by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
+ by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
+ by 0x........: main (origin5-bz2.c:6484)
+ Uninitialised value was created by a client request
+ at 0x........: main (origin5-bz2.c:6479)
+
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2964)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
=================================================
./valgrind-old/memcheck/tests/origin5-bz2.stderr.diff-glibc27-ppc64
=================================================
--- origin5-bz2.stderr.exp-glibc27-ppc64 2009-07-30 07:25:43.000000000 -0500
+++ origin5-bz2.stderr.out 2009-07-30 07:30:47.000000000 -0500
@@ -1,7 +1,7 @@
Conditional jump or move depends on uninitialised value(s)
at 0x........: main (origin5-bz2.c:6481)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
Conditional jump or move depends on uninitialised value(s)
at 0x........: handle_compress (origin5-bz2.c:4686)
@@ -9,85 +9,102 @@
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: handle_compress (origin5-bz2.c:4686)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: handle_compress (origin5-bz2.c:4686)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
- at 0x........: BZ2_blockSort (origin5-bz2.c:2820)
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2820)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
- at 0x........: BZ2_blockSort (origin5-bz2.c:2823)
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2823)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
- at 0x........: BZ2_blockSort (origin5-bz2.c:2854)
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2855)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
- at 0x........: BZ2_blockSort (origin5-bz2.c:2858)
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2859)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
- at 0x........: BZ2_blockSort (origin5-bz2.c:2963)
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2963)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
<truncated beyond 100 lines>
=================================================
./valgrind-old/memcheck/tests/varinfo3.stderr.diff
=================================================
--- varinfo3.stderr.exp 2009-07-30 07:25:44.000000000 -0500
+++ varinfo3.stderr.out 2009-07-30 07:31:28.000000000 -0500
@@ -31,7 +31,7 @@
by 0x........: bar (varinfo3.c:42)
by 0x........: foo (varinfo3.c:58)
by 0x........: main (varinfo3.c:66)
- Address 0x........ is 5 bytes inside data symbol "static_local_def.XXXX"
+ Address 0x........ is in the Data segment of ./varinfo3
Uninitialised byte(s) found during client check request
at 0x........: croak (varinfo3.c:28)
@@ -46,7 +46,7 @@
by 0x........: bar (varinfo3.c:44)
by 0x........: foo (varinfo3.c:58)
by 0x........: main (varinfo3.c:66)
- Address 0x........ is 7 bytes inside data symbol "static_local_undef.XXXX"
+ Address 0x........ is in the Data segment of ./varinfo3
Uninitialised byte(s) found during client check request
at 0x........: croak (varinfo3.c:28)
=================================================
./valgrind-old/memcheck/tests/varinfo5.stderr.diff
=================================================
--- varinfo5.stderr.exp 2009-07-30 07:25:45.000000000 -0500
+++ varinfo5.stderr.out 2009-07-30 07:31:30.000000000 -0500
@@ -119,7 +119,7 @@
by 0x........: varinfo3_main (varinfo5so.c:118)
by 0x........: varinfo5_main (varinfo5so.c:156)
by 0x........: main (varinfo5.c:5)
- Address 0x........ is 5 bytes inside data symbol "static_local_def.XXXX"
+ Address 0x........ is in the Data segment of /Users/coe/src/vg/nightly/valgrind-old/memcheck/tests/varinfo5so.so
Uninitialised byte(s) found during client check request
at 0x........: croak (varinfo5so.c:29)
@@ -138,7 +138,7 @@
by 0x........: varinfo3_main (varinfo5so.c:118)
by 0x........: varinfo5_main (varinfo5so.c:156)
by 0x........: main (varinfo5.c:5)
- Address 0x........ is 7 bytes inside data symbol "static_local_undef.XXXX"
+ Address 0x........ is in the Data segment of /Users/coe/src/vg/nightly/valgrind-old/memcheck/tests/varinfo5so.so
Uninitialised byte(s) found during client check request
at 0x........: croak (varinfo5so.c:29)
=================================================
./valgrind-old/memcheck/tests/vcpu_fnfns.stdout.diff
=================================================
--- vcpu_fnfns.stdout.exp 2009-07-30 07:25:43.000000000 -0500
+++ vcpu_fnfns.stdout.out 2009-07-30 07:31:36.000000000 -0500
@@ -91,16 +91,16 @@
ceilD(-1.2000000008000e+00) = -1.0000000000000e+00
ceilD(-1.1000000009000e+00) = -1.0000000000000e+00
ceilD(-1.0000000010000e+00) = -1.0000000000000e+00
- ceilD(-9.0000000110000e-01) = -0.0000000000000e+00
- ceilD(-8.0000000120000e-01) = -0.0000000000000e+00
- ceilD(-7.0000000130000e-01) = -0.0000000000000e+00
- ceilD(-6.0000000140000e-01) = -0.0000000000000e+00
- ceilD(-5.0000000150000e-01) = -0.0000000000000e+00
- ceilD(-4.0000000160000e-01) = -0.0000000000000e+00
- ceilD(-3.0000000170000e-01) = -0.0000000000000e+00
- ceilD(-2.0000000180000e-01) = -0.0000000000000e+00
- ceilD(-1.0000000190000e-01) = -0.0000000000000e+00
- ceilD(-1.9999992495467e-09) = -0.0000000000000e+00
+ ceilD(-9.0000000110000e-01) = +0.0000000000000e+00
+ ceilD(-8.0000000120000e-01) = +0.0000000000000e+00
+ ceilD(-7.0000000130000e-01) = +0.0000000000000e+00
+ ceilD(-6.0000000140000e-01) = +0.0000000000000e+00
+ ceilD(-5.0000000150000e-01) = +0.0000000000000e+00
+ ceilD(-4.0000000160000e-01) = +0.0000000000000e+00
+ ceilD(-3.0000000170000e-01) = +0.0000000000000e+00
+ ceilD(-2.0000000180000e-01) = +0.0000000000000e+00
+ ceilD(-1.0000000190000e-01) = +0.0000000000000e+00
+ ceilD(-1.9999992495467e-09) = +0.0000000000000e+00
ceilD(+9.9999997900001e-02) = +1.0000000000000e+00
ceilD(+1.9999999780000e-01) = +1.0000000000000e+00
ceilD(+2.9999999770000e-01) = +1.0000000000000e+00
@@ -132,16 +132,16 @@
ceilF( -1.2008e+00) = -1.0000e+00
ceilF( -1.1009e+00) = -1.0000e+00
ceilF( -1.0010e+00) = -1.0000e+00
- ceilF( -9.0110e-01) = -0.0000e+00
- ceilF( -8.0120e-01) = -0.0000e+00
- ceilF( -7.0130e-01) = -0.0000e+00
- ceilF( -6.0140e-01) = -0.0000e+00
- ceilF( -5.0150e-01) = -0.0000e+00
- ceilF( -4.0160e-01) = -0.0000e+00
- ceilF( -3.0170e-01) = -0.0000e+00
- ceilF( -2.0180e-01) = -0.0000e+00
- ceilF( -1.0190e-01) = -0.0000e+00
- ceilF( -1.9999e-03) = -0.0000e+00
+ ceilF( -9.0110e-01) = +0.0000e+00
+ ceilF( -8.0120e-01) = +0.0000e+00
+ ceilF( -7.0130e-01) = +0.0000e+00
+ ceilF( -6.0140e-01) = +0.0000e+00
+ ceilF( -5.0150e-01) = +0.0000e+00
+ ceilF( -4.0160e-01) = +0.0000e+00
+ ceilF( -3.0170e-01) = +0.0000e+00
+ ceilF( -2.0180e-01) = +0.0000e+00
+ ceilF( -1.0190e-01) = +0.0000e+00
+ ceilF( -1.9999e-03) = +0.0000e+00
ceilF( +9.7900e-02) = +1.0000e+00
ceilF( +1.9780e-01) = +1.0000e+00
ceilF( +2.9770e-01) = +1.0000e+00
@@ -305,7 +305,7 @@
cosF( -3.0170e-01) = +9.5483e-01
cosF( -2.0180e-01) = +9.7971e-01
cosF( -1.0190e-01) = +9.9481e-01
- cosF( -1.9999e-03) = +1.0000e-00
+ cosF( -1.9999e-03) = +1.0000e+00
cosF( +9.7900e-02) = +9.9521e-01
cosF( +1.9780e-01) = +9.8050e-01
cosF( +2.9770e-01) = +9.5601e-01
@@ -536,7 +536,7 @@
logD(+9.9999999900000e-02) = -2.3025850939940e+00
logD(+1.9999999980000e-01) = -1.6094379134341e+00
logD(+2.9999999970000e-01) = -1.2039728053259e+00
- logD(+3.9999999960000e-01) = -9.1629073287415e-01
+ logD(+3.9999999960000e-01) = -9.1629073287416e-01
logD(+4.9999999950000e-01) = -6.9314718155995e-01
logD(+5.9999999940000e-01) = -5.1082562476599e-01
logD(+6.9999999930000e-01) = -3.5667494493873e-01
@@ -617,7 +617,7 @@
log10F( +1.8981e+00) = +2.7832e-01
log10F( +1.9980e+00) = +3.0060e-01
asinD(-1.0000000000000e+00) = -1.5707963267949e+00
- asinD(-9.0000000010000e-01) = -1.1197695152281e+00
+ asinD(-9.0000000010000e-01) = -1.1197695152280e+00
asinD(-8.0000000020000e-01) = -9.2729521833495e-01
asinD(-7.0000000030000e-01) = -7.7539749703084e-01
asinD(-6.0000000040000e-01) = -6.4350110929328e-01
=================================================
./valgrind-old/memcheck/tests/vcpu_fnfns.stdout.diff-glibc28-amd64
=================================================
--- vcpu_fnfns.stdout.exp-glibc28-amd64 2009-07-30 07:25:44.000000000 -0500
+++ vcpu_fnfns.stdout.out 2009-07-30 07:31:36.000000000 -0500
@@ -91,16 +91,16 @@
ceilD(-1.2000000008000e+00) = -1.0000000000000e+00
ceilD(-1.1000000009000e+00) = -1.0000000000000e+00
ceilD(-1.0000000010000e+00) = -1.0000000000000e+00
- ceilD(-9.0000000110000e-01) = -0.0000000000000e+00
- ceilD(-8.0000000120000e-01) = -0.0000000000000e+00
- ceilD(-7.0000000130000e-01) = -0.0000000000000e+00
- ceilD(-6.0000000140000e-01) = -0.0000000000000e+00
- ceilD(-5.0000000150000e-01) = -0.0000000000000e+00
- ceilD(-4.0000000160000e-01) = -0.0000000000000e+00
- ceilD(-3.0000000170000e-01) = -0.0000000000000e+00
- ceilD(-2.0000000180000e-01) = -0.0000000000000e+00
- ceilD(-1.0000000190000e-01) = -0.0000000000000e+00
- ceilD(-1.9999992495467e-09) = -0.0000000000000e+00
+ ceilD(-9.0000000110000e-01) = +0.0000000000000e+00
+ ceilD(-8.0000000120000e-01) = +0.0000000000000e+00
+ ceilD(-7.0000000130000e-01) = +0.0000000000000e+00
+ ceilD(-6.0000000140000e-01) = +0.0000000000000e+00
+ ceilD(-5.0000000150000e-01) = +0.0000000000000e+00
+ ceilD(-4.0000000160000e-01) = +0.0000000000000e+00
+ ceilD(-3.0000000170000e-01) = +0.0000000000000e+00
+ ceilD(-2.0000000180000e-01) = +0.0000000000000e+00
+ ceilD(-1.0000000190000e-01) = +0.0000000000000e+00
+ ceilD(-1.9999992495467e-09) = +0.0000000000000e+00
ceilD(+9.9999997900001e-02) = +1.0000000000000e+00
ceilD(+1.9999999780000e-01) = +1.0000000000000e+00
ceilD(+2.9999999770000e-01) = +1.0000000000000e+00
@@ -132,16 +132,16 @@
ceilF( -1.2008e+00) = -1.0000e+00
ceilF( -1.1009e+00) = -1.0000e+00
ceilF( -1.0010e+00) = -1.0000e+00
- ceilF( -9.0110e-01) = -0.0000e+00
- ceilF( -8.0120e-01) = -0.0000e+00
- ceilF( -7.0130e-01) = -0.0000e+00
- ceilF( -6.0140e-01) = -0.0000e+00
- ceilF( -5.0150e-01) = -0.0000e+00
- ceilF( -4.0160e-01) = -0.0000e+00
- ceilF( -3.0170e-01) = -0.0000e+00
- ceilF( -2.0180e-01) = -0.0000e+00
- ceilF( -1.0190e-01) = -0.0000e+00
- ceilF( -1.9999e-03) = -0.0000e+00
+ ceilF( -9.0110e-01) = +0.0000e+00
+ ceilF( -8.0120e-01) = +0.0000e+00
+ ceilF( -7.0130e-01) = +0.0000e+00
+ ceilF( -6.0140e-01) = +0.0000e+00
+ ceilF( -5.0150e-01) = +0.0000e+00
+ ceilF( -4.0160e-01) = +0.0000e+00
+ ceilF( -3.0170e-01) = +0.0000e+00
+ ceilF( -2.0180e-01) = +0.0000e+00
+ ceilF( -1.0190e-01) = +0.0000e+00
+ ceilF( -1.9999e-03) = +0.0000e+00
ceilF( +9.7900e-02) = +1.0000e+00
ceilF( +1.9780e-01) = +1.0000e+00
ceilF( +2.9770e-01) = +1.0000e+00
@@ -536,7 +536,7 @@
logD(+9.9999999900000e-02) = -2.3025850939940e+00
logD(+1.9999999980000e-01) = -1.6094379134341e+00
logD(+2.9999999970000e-01) = -1.2039728053259e+00
- logD(+3.9999999960000e-01) = -9.1629073287415e-01
+ logD(+3.9999999960000e-01) = -9.1629073287416e-01
logD(+4.9999999950000e-01) = -6.9314718155995e-01
logD(+5.9999999940000e-01) = -5.1082562476599e-01
logD(+6.9999999930000e-01) = -3.5667494493873e-01
@@ -617,7 +617,7 @@
log10F( +1.8981e+00) = +2.7832e-01
log10F( +1.9980e+00) = +3.0060e-01
asinD(-1.0000000000000e+00) = -1.5707963267949e+00
- asinD(-9.0000000010000e-01) = -1.1197695152281e+00
+ asinD(-9.0000000010000e-01) = -1.1197695152280e+00
asinD(-8.0000000020000e-01) = -9.2729521833495e-01
asinD(-7.0000000030000e-01) = -7.7539749703084e-01
asinD(-6.0000000040000e-01) = -6.4350110929328e-01
=================================================
./valgrind-old/none/tests/async-sigs.stderr.diff
=================================================
--- async-sigs.stderr.exp 2009-07-30 07:25:55.000000000 -0500
+++ async-sigs.stderr.out 2009-07-30 07:32:41.000000000 -0500
@@ -1,8 +1,30 @@
-testing: blocking=0 caught=11 fatal=7... PASSED
+testing: blocking=0 caught=11 fatal=10...
+Process terminating with default action of signal 10 (SIGBUS)
+ Non-existent physical address at address 0x........
+ at 0x........: test (async-sigs.c:94)
+ by 0x........: main (async-sigs.c:129)
+PASSED
testing: blocking=0 caught=11 fatal=1... PASSED
-testing: blocking=0 caught=10 fatal=7... PASSED
-testing: blocking=0 caught=10 fatal=1... PASSED
-testing: blocking=1 caught=11 fatal=7... PASSED
+testing: blocking=0 caught=30 fatal=10...
+Process terminating with default action of signal 10 (SIGBUS)
+ Non-existent physical address at address 0x........
+ at 0x........: test (async-sigs.c:94)
+ by 0x........: main (async-sigs.c:131)
+PASSED
+testing: blocking=0 caught=30 fatal=1... PASSED
+testing: blocking=1 caught=11 fatal=10...
+Process terminating with default action of signal 10 (SIGBUS)
+ Non-existent physical address at address 0x........
+ at 0x........: __sigsuspend (in /...libc...)
+ by 0x........: test (async-sigs.c:95)
+ by 0x........: main (async-sigs.c:133)
+PASSED
testing: blocking=1 caught=11 fatal=1... PASSED
-testing: blocking=1 caught=10 fatal=7... PASSED
-testing: blocking=1 caught=10 fatal=1... PASSED
+testing: blocking=1 caught=30 fatal=10...
+Process terminating with default action of signal 10 (SIGBUS)
+ Non-existent physical address at address 0x........
+ at 0x........: __sigsuspend (in /...libc...)
+ by 0x........: test (async-sigs.c:95)
+ by 0x........: main (async-sigs.c:135)
+PASSED
+testing: blocking=1 caught=30 fatal=1... PASSED
=================================================
./valgrind-old/none/tests/faultstatus.stderr.diff
=================================================
--- faultstatus.stderr.exp 2009-07-30 07:25:57.000000000 -0500
+++ faultstatus.stderr.out 2009-07-30 07:32:45.000000000 -0500
@@ -1,6 +1,6 @@
-Test 1: PASS
-Test 2: PASS
-Test 3: PASS
-Test 4: PASS
+Test 1: FAIL: expected signal 11, not 10
+Test 2: FAIL: expected signal 11, not 10
+Test 3: FAIL: no fault, or handler returned
+Test 4: FAIL: expected si_code==7, not 0
=================================================
./valgrind-old/none/tests/pth_blockedsig.stderr.diff
=================================================
--- pth_blockedsig.stderr.exp 2009-07-30 07:25:55.000000000 -0500
+++ pth_blockedsig.stderr.out 2009-07-30 07:33:39.000000000 -0500
@@ -1,2 +1,4 @@
+UNKNOWN __pthread_sigmask is unsupported. This warning will not be repeated.
+SHOULD NOT BE HERE (SIGUSR1)!!!!
|
|
From: Nicholas N. <n.n...@gm...> - 2009-07-30 11:48:14
|
On Thu, Jul 30, 2009 at 8:34 PM, Bart Van Assche<bar...@gm...> wrote: > > Another issue (probably a long-standing issue) that I noticed yesterday is > that the backtraces printed by Valgrind seem to depend on subtleties of the > platform Valgrind is running on. On some platforms I see the filename and > linenumber for the stackframe referring to main() (as expected), sometimes I > see "(below main)" printed for the stackframe referring to main() (not > expected). If you use --show-below-main in the latter case you'll get the actual symbol names. Doesn't explain the difference, though. Could be a compiler difference. Nick |
|
From: Bart V. A. <bar...@gm...> - 2009-07-30 10:34:20
|
On Thu, Jul 30, 2009 at 11:30 AM, Tom Hughes <to...@co...> wrote: > On 30/07/09 06:58, Bart Van Assche wrote: > > Any idea why your patch changes the output of the >> memcheck/tests/x86/pushfpopf regression test ? With your patch applied >> Valgrind prints one stackframe less for this regression test. The diff >> I get is as follows (x86_64, gcc 4.4.1): >> > > Because it was a tad bogus - the am_is_readable routine expected start and > length but the stack unwinder was passing it start and end instead. > > The attached one should work a bit better... > Thanks for the quick update. With the second version of the valgrind-isreadable.patch the output of "make regtest" is now the same as without this patch on openSUSE 11.1. Another issue (probably a long-standing issue) that I noticed yesterday is that the backtraces printed by Valgrind seem to depend on subtleties of the platform Valgrind is running on. On some platforms I see the filename and linenumber for the stackframe referring to main() (as expected), sometimes I see "(below main)" printed for the stackframe referring to main() (not expected). An example: With openSUSE 11.1 x86_64: $ ./vg-in-place --tool=drd --check-stack-var=yes helgrind/tests/tc09_bad_unlock ... ==13368== Destroying locked mutex: mutex 0x7fefffb70, recursion count 1, owner 1. ==13368== at 0x40085E: nearly_main (tc09_bad_unlock.c:45) ==13368== by 0x400868: main (tc09_bad_unlock.c:49) ... With openSUSE 11.0 x86_64: $ ./vg-in-place --tool=drd --check-stack-var=yes helgrind/tests/tc09_bad_unlock ... ==23627== Destroying locked mutex: mutex 0x7ff000070, recursion count 1, owner 1. ==23627== at 0x40085E: nearly_main (tc09_bad_unlock.c:45) ==23627== by 0x5067585: (below main) (in /lib64/libc-2.9.so) ... Any idea what might be the cause of this last issue ? Bart. |
|
From: Tom H. <to...@co...> - 2009-07-30 09:30:26
|
On 30/07/09 06:58, Bart Van Assche wrote: > Any idea why your patch changes the output of the > memcheck/tests/x86/pushfpopf regression test ? With your patch applied > Valgrind prints one stackframe less for this regression test. The diff > I get is as follows (x86_64, gcc 4.4.1): Because it was a tad bogus - the am_is_readable routine expected start and length but the stack unwinder was passing it start and end instead. The attached one should work a bit better... Tom -- Tom Hughes (to...@co...) http://www.compton.nu/ |
|
From: Bart V. A. <bar...@gm...> - 2009-07-30 07:58:28
|
Nightly build on georgia-tech-cellbuzz-native ( cellbuzz, ppc64, Fedora 7, native ) Started at 2009-07-30 02:15:14 EDT Ended at 2009-07-30 03:58:08 EDT Results differ from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... done Regression test results follow == 437 tests, 44 stderr failures, 9 stdout failures, 0 post failures == memcheck/tests/deep_templates (stdout) memcheck/tests/leak-cases-full (stderr) memcheck/tests/leak-cases-summary (stderr) memcheck/tests/leak-cycle (stderr) memcheck/tests/origin5-bz2 (stderr) memcheck/tests/varinfo1 (stderr) memcheck/tests/varinfo2 (stderr) memcheck/tests/varinfo3 (stderr) memcheck/tests/varinfo4 (stderr) memcheck/tests/varinfo5 (stderr) memcheck/tests/varinfo6 (stderr) memcheck/tests/wrap8 (stderr) none/tests/empty-exe (stderr) none/tests/linux/mremap (stderr) none/tests/ppc32/jm-fp (stdout) none/tests/ppc32/jm-vmx (stdout) none/tests/ppc32/round (stdout) none/tests/ppc32/test_gx (stdout) none/tests/ppc64/jm-fp (stdout) none/tests/ppc64/jm-vmx (stdout) none/tests/ppc64/round (stdout) none/tests/shell (stdout) none/tests/shell (stderr) none/tests/shell_valid1 (stderr) none/tests/shell_valid2 (stderr) none/tests/shell_valid3 (stderr) none/tests/shell_zerolength (stderr) helgrind/tests/hg05_race2 (stderr) helgrind/tests/tc06_two_races_xml (stderr) helgrind/tests/tc22_exit_w_lock (stderr) helgrind/tests/tc23_bogus_condwait (stderr) exp-ptrcheck/tests/bad_percentify (stderr) exp-ptrcheck/tests/base (stderr) exp-ptrcheck/tests/ccc (stderr) exp-ptrcheck/tests/fp (stderr) exp-ptrcheck/tests/globalerr (stderr) exp-ptrcheck/tests/hackedbz2 (stderr) exp-ptrcheck/tests/hp_bounds (stderr) exp-ptrcheck/tests/hp_dangle (stderr) exp-ptrcheck/tests/hsg (stderr) exp-ptrcheck/tests/justify (stderr) exp-ptrcheck/tests/partial_bad (stderr) exp-ptrcheck/tests/partial_good (stderr) exp-ptrcheck/tests/preen_invars (stderr) exp-ptrcheck/tests/pth_create (stderr) exp-ptrcheck/tests/pth_specific (stderr) exp-ptrcheck/tests/realloc (stderr) exp-ptrcheck/tests/stackerr (stderr) exp-ptrcheck/tests/strcpy (stderr) exp-ptrcheck/tests/supp (stderr) exp-ptrcheck/tests/tricky (stderr) exp-ptrcheck/tests/unaligned (stderr) exp-ptrcheck/tests/zero (stderr) ================================================= == Results from 24 hours ago == ================================================= Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... done Regression test results follow == 436 tests, 44 stderr failures, 9 stdout failures, 0 post failures == memcheck/tests/deep_templates (stdout) memcheck/tests/leak-cases-full (stderr) memcheck/tests/leak-cases-summary (stderr) memcheck/tests/leak-cycle (stderr) memcheck/tests/origin5-bz2 (stderr) memcheck/tests/varinfo1 (stderr) memcheck/tests/varinfo2 (stderr) memcheck/tests/varinfo3 (stderr) memcheck/tests/varinfo4 (stderr) memcheck/tests/varinfo5 (stderr) memcheck/tests/varinfo6 (stderr) memcheck/tests/wrap8 (stderr) none/tests/empty-exe (stderr) none/tests/linux/mremap (stderr) none/tests/ppc32/jm-fp (stdout) none/tests/ppc32/jm-vmx (stdout) none/tests/ppc32/round (stdout) none/tests/ppc32/test_gx (stdout) none/tests/ppc64/jm-fp (stdout) none/tests/ppc64/jm-vmx (stdout) none/tests/ppc64/round (stdout) none/tests/shell (stdout) none/tests/shell (stderr) none/tests/shell_valid1 (stderr) none/tests/shell_valid2 (stderr) none/tests/shell_valid3 (stderr) none/tests/shell_zerolength (stderr) helgrind/tests/hg05_race2 (stderr) helgrind/tests/tc06_two_races_xml (stderr) helgrind/tests/tc22_exit_w_lock (stderr) helgrind/tests/tc23_bogus_condwait (stderr) exp-ptrcheck/tests/bad_percentify (stderr) exp-ptrcheck/tests/base (stderr) exp-ptrcheck/tests/ccc (stderr) exp-ptrcheck/tests/fp (stderr) exp-ptrcheck/tests/globalerr (stderr) exp-ptrcheck/tests/hackedbz2 (stderr) exp-ptrcheck/tests/hp_bounds (stderr) exp-ptrcheck/tests/hp_dangle (stderr) exp-ptrcheck/tests/hsg (stderr) exp-ptrcheck/tests/justify (stderr) exp-ptrcheck/tests/partial_bad (stderr) exp-ptrcheck/tests/partial_good (stderr) exp-ptrcheck/tests/preen_invars (stderr) exp-ptrcheck/tests/pth_create (stderr) exp-ptrcheck/tests/pth_specific (stderr) exp-ptrcheck/tests/realloc (stderr) exp-ptrcheck/tests/stackerr (stderr) exp-ptrcheck/tests/strcpy (stderr) exp-ptrcheck/tests/supp (stderr) exp-ptrcheck/tests/tricky (stderr) exp-ptrcheck/tests/unaligned (stderr) exp-ptrcheck/tests/zero (stderr) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Thu Jul 30 03:06:40 2009 --- new.short Thu Jul 30 03:58:08 2009 *************** *** 8,10 **** ! == 436 tests, 44 stderr failures, 9 stdout failures, 0 post failures == memcheck/tests/deep_templates (stdout) --- 8,10 ---- ! == 437 tests, 44 stderr failures, 9 stdout failures, 0 post failures == memcheck/tests/deep_templates (stdout) |
|
From: Bart V. A. <bar...@gm...> - 2009-07-30 05:58:18
|
On Wed, Jul 29, 2009 at 1:14 PM, Tom Hughes <to...@co...> wrote:
>
> On 29/07/09 11:57, sv...@va... wrote:
>
>> +# Like Tom says, the stack unwinder protection is bollocks.
>> +# We should junk all previous schemes and simply get the
>> +# stack unwinder to consult aspacem at each frame (cache-accelerated,
>> +# of course) to check each page it visits is accessible.
>
> I have a patch to do that ;-)
>
> I've attached it - it doesn't do any caching at the moment though.
>
> Of course we should also try and unify the two different stack tracking schemes and generally try and do a better job of knowing where the stack for each thread is.
Hello Tom,
Any idea why your patch changes the output of the
memcheck/tests/x86/pushfpopf regression test ? With your patch applied
Valgrind prints one stackframe less for this regression test. The diff
I get is as follows (x86_64, gcc 4.4.1):
$ cat memcheck/tests/x86/pushfpopf*diff*
--- pushfpopf.stderr.exp 2009-03-01 11:51:11.000000000 +0100
+++ pushfpopf.stderr.out 2009-07-30 07:32:14.000000000 +0200
@@ -1,7 +1,5 @@
Conditional jump or move depends on uninitialised value(s)
at 0x........: fooble (...)
- by 0x........: main (pushfpopf_c.c:12)
Conditional jump or move depends on uninitialised value(s)
at 0x........: fooble (...)
- by 0x........: main (pushfpopf_c.c:12)
Bart.
|
|
From: <sv...@va...> - 2009-07-30 04:48:18
|
Author: njn Date: 2009-07-30 05:48:05 +0100 (Thu, 30 Jul 2009) New Revision: 10665 Log: Use <variablelist> for ms_print's and cg_annotate's options list. Modified: trunk/cachegrind/docs/cg-manual.xml trunk/massif/docs/ms-manual.xml Modified: trunk/cachegrind/docs/cg-manual.xml =================================================================== --- trunk/cachegrind/docs/cg-manual.xml 2009-07-30 04:27:26 UTC (rev 10664) +++ trunk/cachegrind/docs/cg-manual.xml 2009-07-30 04:48:05 UTC (rev 10665) @@ -836,78 +836,109 @@ <sect1 id="cg-manual.annopts" xreflabel="cg_annotate options"> <title>cg_annotate options</title> -<itemizedlist> +<variablelist> - <listitem> - <para><option>-h --help</option></para> - <para><option>-v --version</option></para> - <para>Help and version, as usual.</para> - </listitem> + <varlistentry> + <term> + <option><![CDATA[-h --help ]]></option> + </term> + <listitem> + <para>Show the help message.</para> + </listitem> + </varlistentry> - <listitem id="sort"> - <para><option>--sort=A,B,C</option> [default: - order in - <computeroutput>cachegrind.out.<pid></computeroutput>]</para> - <para>Specifies the events upon which the sorting of the - function-by-function entries will be based. Useful if you - want to concentrate on eg. I cache misses - (<option>--sort=I1mr,I2mr</option>), or D cache misses - (<option>--sort=D1mr,D2mr</option>), or L2 misses - (<option>--sort=D2mr,I2mr</option>).</para> - </listitem> + <varlistentry> + <term> + <option><![CDATA[-v --version ]]></option> + </term> + <listitem> + <para>Show the version number.</para> + </listitem> + </varlistentry> - <listitem id="show"> - <para><option>--show=A,B,C</option> [default: - all, using order in - <computeroutput>cachegrind.out.<pid></computeroutput>]</para> - <para>Specifies which events to show (and the column - order). Default is to use all present in the - <computeroutput>cachegrind.out.<pid></computeroutput> file (and - use the order in the file).</para> - </listitem> + <varlistentry> + <term> + <option><![CDATA[--sort=A,B,C [default: order in + cachegrind.out.<pid>] ]]></option> + </term> + <listitem> + <para>Specifies the events upon which the sorting of the + function-by-function entries will be based. Useful if you + want to concentrate on eg. I cache misses + (<option>--sort=I1mr,I2mr</option>), or D cache misses + (<option>--sort=D1mr,D2mr</option>), or L2 misses + (<option>--sort=D2mr,I2mr</option>).</para> + </listitem> + </varlistentry> - <listitem id="threshold"> - <para><option>--threshold=X</option> - [default: 99%]</para> - <para>Sets the threshold for the function-by-function - summary. Functions are shown that account for more than X% - of the primary sort event. If auto-annotating, also affects - which files are annotated.</para> - - <para>Note: thresholds can be set for more than one of the - events by appending any events for the - <option>--sort</option> option with a colon - and a number (no spaces, though). E.g. if you want to see - the functions that cover 99% of L2 read misses and 99% of L2 - write misses, use this option:</para> - <para><option>--sort=D2mr:99,D2mw:99</option></para> - </listitem> + <varlistentry> + <term> + <option><![CDATA[--show=A,B,C [default: all, using order in + cachegrind.out.<pid>] ]]></option> + </term> + <listitem> + <para>Specifies which events to show (and the column + order). Default is to use all present in the + <computeroutput>cachegrind.out.<pid></computeroutput> file (and + use the order in the file).</para> + </listitem> + </varlistentry> - <listitem id="auto"> - <para><option>--auto=no</option> [default]</para> - <para><option>--auto=yes</option></para> - <para>When enabled, automatically annotates every file that - is mentioned in the function-by-function summary that can be - found. Also gives a list of those that couldn't be found.</para> - </listitem> + <varlistentry> + <term> + <option><![CDATA[--threshold=X [default: 99%] ]]></option> + </term> + <listitem> + <para>Sets the threshold for the function-by-function + summary. Functions are shown that account for more than X% + of the primary sort event. If auto-annotating, also affects + which files are annotated.</para> + + <para>Note: thresholds can be set for more than one of the + events by appending any events for the + <option>--sort</option> option with a colon + and a number (no spaces, though). E.g. if you want to see + the functions that cover 99% of L2 read misses and 99% of L2 + write misses, use this option:</para> + <para><option>--sort=D2mr:99,D2mw:99</option></para> + </listitem> + </varlistentry> - <listitem id="context"> - <para><option>--context=N</option> [default: 8]</para> - <para>Print N lines of context before and after each - annotated line. Avoids printing large sections of source - files that were not executed. Use a large number - (eg. 10,000) to show all source lines.</para> - </listitem> + <varlistentry> + <term> + <option><![CDATA[--auto=<no|yes> [default: no] ]]></option> + </term> + <listitem> + <para>When enabled, automatically annotates every file that + is mentioned in the function-by-function summary that can be + found. Also gives a list of those that couldn't be found.</para> + </listitem> + </varlistentry> - <listitem id="include"> - <para><option>-I<dir>, --include=<dir></option> - [default: empty string]</para> - <para>Adds a directory to the list in which to search for - files. Multiple -I/--include options can be given to add - multiple directories.</para> - </listitem> + <varlistentry> + <term> + <option><![CDATA[--context=N [default: 8] ]]></option> + </term> + <listitem> + <para>Print N lines of context before and after each + annotated line. Avoids printing large sections of source + files that were not executed. Use a large number + (eg. 10,000) to show all source lines.</para> + </listitem> + </varlistentry> -</itemizedlist> + <varlistentry> + <term> + <option><![CDATA[-I<dir> --include=<dir> [default: none] ]]></option> + </term> + <listitem> + <para>Adds a directory to the list in which to search for + files. Multiple -I/--include options can be given to add + multiple directories.</para> + </listitem> + </varlistentry> + +</variablelist> Modified: trunk/massif/docs/ms-manual.xml =================================================================== --- trunk/massif/docs/ms-manual.xml 2009-07-30 04:27:26 UTC (rev 10664) +++ trunk/massif/docs/ms-manual.xml 2009-07-30 04:48:05 UTC (rev 10665) @@ -718,32 +718,56 @@ <para>ms_print's options are:</para> -<itemizedlist> +<variablelist> - <listitem> - <para><option>-h --help</option></para> - <para><option>-v --version</option></para> - <para>Help and version, as usual.</para> - </listitem> + <varlistentry> + <term> + <option><![CDATA[-h --help ]]></option> + </term> + <listitem> + <para>Show the help message.</para> + </listitem> + </varlistentry> - <listitem> - <para><option><![CDATA[--threshold=<m.n>]]></option> [default: 1.0]</para> - <para>Same as Massif's <option>--threshold</option>, but - applied after profiling rather than during.</para> - </listitem> + <varlistentry> + <term> + <option><![CDATA[-v --version ]]></option> + </term> + <listitem> + <para>Show the version number.</para> + </listitem> + </varlistentry> - <listitem> - <para><option><![CDATA[--x=<m.n>]]></option> [default: 72]</para> - <para>Width of the graph, in columns.</para> - </listitem> + <varlistentry> + <term> + <option><![CDATA[--threshold=<m.n> [default: 1.0] ]]></option> + </term> + <listitem> + <para>Same as Massif's <option>--threshold</option> option, but + applied after profiling rather than during.</para> + </listitem> + </varlistentry> - <listitem> - <para><option><![CDATA[--y=<n>]]></option> [default: 20]</para> - <para>Height of the graph, in rows.</para> - </listitem> + <varlistentry> + <term> + <option><![CDATA[--x=<n> [default: 72]]]></option> + </term> + <listitem> + <para>Width of the graph, in columns.</para> + </listitem> + </varlistentry> -</itemizedlist> + <varlistentry> + <term> + <option><![CDATA[--y=<n> [default: 20] ]]></option> + </term> + <listitem> + <para>Height of the graph, in rows.</para> + </listitem> + </varlistentry> +</variablelist> + </sect1> <sect1 id="ms-manual.fileformat" xreflabel="fileformat"> |
|
From: <sv...@va...> - 2009-07-30 04:27:47
|
Author: njn Date: 2009-07-30 05:27:26 +0100 (Thu, 30 Jul 2009) New Revision: 10664 Log: Man page fix. Modified: trunk/docs/xml/valgrind-manpage.xml Modified: trunk/docs/xml/valgrind-manpage.xml =================================================================== --- trunk/docs/xml/valgrind-manpage.xml 2009-07-30 04:25:02 UTC (rev 10663) +++ trunk/docs/xml/valgrind-manpage.xml 2009-07-30 04:27:26 UTC (rev 10664) @@ -142,9 +142,6 @@ <title>Callgrind Options</title> <xi:include href="../../callgrind/docs/cl-manual.xml" - xpointer="cl.opts.list.misc" - xmlns:xi="http://www.w3.org/2001/XInclude" /> -<xi:include href="../../callgrind/docs/cl-manual.xml" xpointer="cl.opts.list.creation" xmlns:xi="http://www.w3.org/2001/XInclude" /> <xi:include href="../../callgrind/docs/cl-manual.xml" |
|
From: <sv...@va...> - 2009-07-30 04:25:14
|
Author: njn
Date: 2009-07-30 05:25:02 +0100 (Thu, 30 Jul 2009)
New Revision: 10663
Log:
Remove some not-very useful info that tends to get out of date.
Modified:
trunk/massif/docs/ms-manual.xml
Modified: trunk/massif/docs/ms-manual.xml
===================================================================
--- trunk/massif/docs/ms-manual.xml 2009-07-30 04:22:09 UTC (rev 10662)
+++ trunk/massif/docs/ms-manual.xml 2009-07-30 04:25:02 UTC (rev 10663)
@@ -587,26 +587,6 @@
--alloc-fn='operator new(unsigned, std::nothrow_t const&)'
]]></screen>
</para>
-
- <para>
- The full list of functions and operators that are by default
- considered allocation functions is as follows.</para>
-<screen><
-operator new[](unsigned long)
-operator new(unsigned, std::nothrow_t const&)
-operator new[](unsigned, std::nothrow_t const&)
-operator new(unsigned long, std::nothrow_t const&)
-operator new[](unsigned long, std::nothrow_t const&)
-]]></screen>
</listitem>
</varlistentry>
|
|
From: <sv...@va...> - 2009-07-30 04:22:22
|
Author: njn
Date: 2009-07-30 05:22:09 +0100 (Thu, 30 Jul 2009)
New Revision: 10662
Log:
Remove lots of boilerplate text (tool descriptions) that tends to get out of
date from the man page.
Make the man page match the ordering in the user manual.
Put Nulgrind last in the user manual.
Modified:
trunk/docs/xml/manual.xml
trunk/docs/xml/valgrind-manpage.xml
Modified: trunk/docs/xml/manual.xml
===================================================================
--- trunk/docs/xml/manual.xml 2009-07-30 04:07:10 UTC (rev 10661)
+++ trunk/docs/xml/manual.xml 2009-07-30 04:22:09 UTC (rev 10662)
@@ -40,9 +40,9 @@
xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="../../exp-bbv/docs/bbv-manual.xml" parse="xml"
xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="../../lackey/docs/lk-manual.xml" parse="xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="../../none/docs/nl-manual.xml" parse="xml"
xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="../../lackey/docs/lk-manual.xml" parse="xml"
- xmlns:xi="http://www.w3.org/2001/XInclude" />
</book>
Modified: trunk/docs/xml/valgrind-manpage.xml
===================================================================
--- trunk/docs/xml/valgrind-manpage.xml 2009-07-30 04:07:10 UTC (rev 10661)
+++ trunk/docs/xml/valgrind-manpage.xml 2009-07-30 04:22:09 UTC (rev 10662)
@@ -20,14 +20,9 @@
<refsynopsisdiv>
<cmdsynopsis>
<command>valgrind</command>
- <arg>
- <arg><replaceable>valgrind</replaceable></arg>
- <arg><replaceable>options</replaceable></arg>
- </arg>
- <arg><replaceable>your-program</replaceable></arg>
- <arg>
- <arg><replaceable>your-program-options</replaceable></arg>
- </arg>
+ <arg><replaceable>valgrind-options</replaceable></arg>
+ <arg><command>your-program</command></arg>
+ <arg><replaceable>your-program-options</replaceable></arg>
</cmdsynopsis>
</refsynopsisdiv>
@@ -37,11 +32,14 @@
<para><command>Valgrind</command> is a flexible program for debugging
and profiling Linux executables. It consists of a core, which provides
-a synthetic CPU in software, and a series of "tools", each of which is a
-debugging or profiling tool. The architecture is modular, so that new
-tools can be created easily and without disturbing the existing
-structure.</para>
+a synthetic CPU in software, and a series of debugging and profiling tools.
+The architecture is modular, so that new tools can be created easily and
+without disturbing the existing structure.</para>
+<para>Some of the options described below work with all Valgrind tools, and
+some only work with a few or one. The section MEMCHECK OPTIONS and those
+below it describe tool-specific options.</para>
+
<para>This manual page covers only basic usage and options. For more
comprehensive information, please see the HTML documentation on your
system: <filename>&vg-doc-path;</filename>, or online:
@@ -50,73 +48,7 @@
</refsect1>
-<refsect1 id="invocation">
-<title>Invocation</title>
-<para><command>Valgrind</command> is typically invoked as follows:
-<literallayout> valgrind program args</literallayout>
-
-This runs <command>program</command> (with arguments
-<command>args</command>) under Valgrind using the Memcheck tool.
-Memcheck performs a range of memory-checking functions, including
-detecting accesses to uninitialised memory, misuse of allocated memory
-(double frees, access after free, etc.) and detecting memory
-leaks.</para>
-
-<para>To use a different tool, use the <option>--tool</option> option:
-<literallayout> valgrind --tool=toolname program args</literallayout></para>
-
-<para>The following tools are available:</para>
-
-<itemizedlist>
-
- <listitem>
- <para><option>cachegrind</option> is a cache simulator. It can be
- used to annotate every line of your program with the number of
- instructions executed and cache misses incurred.</para>
- </listitem>
-
- <listitem>
- <para><option>callgrind</option> adds call graph tracing to cachegrind. It can be
- used to get call counts and inclusive cost for each call happening in your
- program. In addition to cachegrind, callgrind can annotate threads separately,
- and every instruction of disassembler output of your program with the number of
- instructions executed and cache misses incurred.</para>
- </listitem>
-
- <listitem>
- <para><option>helgrind</option> spots potential race conditions in
- your program.</para>
- </listitem>
-
- <listitem>
- <para><option>lackey</option> is a sample tool that can be used as a
- template for generating your own tools. After the program
- terminates, it prints out some basic statistics about the program
- execution.</para>
- </listitem>
-
- <listitem>
- <para><option>massif</option> is a heap profiler. It measures how
- much heap memory your program uses.</para>
- </listitem>
-
- <listitem>
- <para><option>memcheck</option> is a fine-grained memory checker.</para>
- </listitem>
-
- <listitem>
- <para><option>none</option> performs no function - it simply runs
- the program under Valgrind. This is typically used for debugging
- and benchmarking Valgrind.</para>
- </listitem>
-
-</itemizedlist>
-
-</refsect1>
-
-
-
<refsect1 id="basic-options">
<title>Basic Options</title>
@@ -228,28 +160,39 @@
-<refsect1 id="massif-options">
-<title>Massif Options</title>
+<refsect1 id="helgrind-options">
+<title>Helgrind Options</title>
-<xi:include href="../../massif/docs/ms-manual.xml"
- xpointer="ms.opts.list"
+<xi:include href="../../helgrind/docs/hg-manual.xml"
+ xpointer="hg.opts.list"
xmlns:xi="http://www.w3.org/2001/XInclude" />
</refsect1>
-<refsect1 id="helgrind-options">
-<title>Helgrind Options</title>
+<refsect1 id="drd-options">
+<title>DRD Options</title>
-<xi:include href="../../helgrind/docs/hg-manual.xml"
- xpointer="hg.opts.list"
+<xi:include href="../../drd/docs/drd-manual.xml"
+ xpointer="drd.opts.list"
xmlns:xi="http://www.w3.org/2001/XInclude" />
</refsect1>
+<refsect1 id="massif-options">
+<title>Massif Options</title>
+
+<xi:include href="../../massif/docs/ms-manual.xml"
+ xpointer="ms.opts.list"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
+
+</refsect1>
+
+
+
<refsect1 id="ptrcheck-options">
<title>Ptrcheck Options</title>
|
|
From: <sv...@va...> - 2009-07-30 04:07:24
|
Author: njn Date: 2009-07-30 05:07:10 +0100 (Thu, 30 Jul 2009) New Revision: 10661 Log: Unbreak 'make dist'. Modified: trunk/exp-bbv/tests/amd64-linux/Makefile.am Modified: trunk/exp-bbv/tests/amd64-linux/Makefile.am =================================================================== --- trunk/exp-bbv/tests/amd64-linux/Makefile.am 2009-07-30 03:21:42 UTC (rev 10660) +++ trunk/exp-bbv/tests/amd64-linux/Makefile.am 2009-07-30 04:07:10 UTC (rev 10661) @@ -27,7 +27,7 @@ LDFLAGS += -nostartfiles -nodefaultlibs -clone_test = clone_test.S +clone_test_SOURCES = clone_test.S complex_rep_SOURCES = complex_rep.S fldcw_check_SOURCES = fldcw_check.S ll_SOURCES = ll.S |
|
From: <sv...@va...> - 2009-07-30 03:21:57
|
Author: njn
Date: 2009-07-30 04:21:42 +0100 (Thu, 30 Jul 2009)
New Revision: 10660
Log:
Improve the "acting on Cachegrind's info" section.
Modified:
trunk/cachegrind/docs/cg-manual.xml
Modified: trunk/cachegrind/docs/cg-manual.xml
===================================================================
--- trunk/cachegrind/docs/cg-manual.xml 2009-07-30 02:57:52 UTC (rev 10659)
+++ trunk/cachegrind/docs/cg-manual.xml 2009-07-30 03:21:42 UTC (rev 10660)
@@ -1198,9 +1198,8 @@
xreflabel="Acting on Cachegrind's information">
<title>Acting on Cachegrind's information</title>
<para>
-So, you've managed to profile your program with Cachegrind. Now what?
-What's the best way to actually act on the information it provides to speed
-up your program? Here are some rules of thumb that we have found to be
+Cachegrind gives you lots of information, but acting on that information
+isn't always easy. Here are some rules of thumb that we have found to be
useful.</para>
<para>
@@ -1210,6 +1209,17 @@
Otherwise, they're not enough to act on.</para>
<para>
+The function-by-function counts are more useful to look at, as they pinpoint
+which functions are causing large numbers of counts. However, beware that
+inlining can make these counts misleading. If a function
+<function>f</function> is always inlined, counts will be attributed to the
+functions it is inlined into, rather than itself. However, if you look at
+the line-by-line annotations for <function>f</function> you'll see the
+counts that belong to <function>f</function>. (This is hard to avoid, it's
+how the debug info is structured.) So it's worth looking for large numbers
+in the line-by-line annotations.</para>
+
+<para>
The line-by-line source code annotations are much more useful. In our
experience, the best place to start is by looking at the
<computeroutput>Ir</computeroutput> numbers. They simply measure how many
@@ -1220,13 +1230,53 @@
<para>
After that, we have found that L2 misses are typically a much bigger source
of slow-downs than L1 misses. So it's worth looking for any snippets of
-code that cause a high proportion of the L2 misses. If you find any, it's
-still not always easy to work out how to improve things. You need to have a
+code with high <computeroutput>D2mr</computeroutput> or
+<computeroutput>D2mw</computeroutput> counts. (You can use
+<option>--show=D2mr
+--sort=D2mr</option> with cg_annotate to focus just on
+<literal>D2mr</literal> counts, for example.) If you find any, it's still
+not always easy to work out how to improve things. You need to have a
reasonable understanding of how caches work, the principles of locality, and
your program's data access patterns. Improving things may require
redesigning a data structure, for example.</para>
<para>
+Looking at the <computeroutput>Bcm</computeroutput> and
+<computeroutput>Bim</computeroutput> misses can also be helpful.
+In particular, <computeroutput>Bim</computeroutput> misses are often caused
+by <literal>switch</literal> statements, and in some cases these
+<literal>switch</literal> statements can be replaced with table-driven code.
+For example, you might replace code like this:</para>
+
+<programlisting><![CDATA[
+enum E { A, B, C };
+enum E e;
+int i;
+...
+switch (e)
+{
+ case A: i += 1;
+ case B: i += 2;
+ case C: i += 3;
+}
+]]></programlisting>
+
+<para>with code like this:</para>
+
+<programlisting><![CDATA[
+enum E { A, B, C };
+enum E e;
+enum E table[] = { 1, 2, 3 };
+int i;
+...
+i += table[e];
+]]></programlisting>
+
+<para>
+This is obviously a contrived example, but the basic principle applies in a
+wide variety of situations.</para>
+
+<para>
In short, Cachegrind can tell you where some of the bottlenecks in your code
are, but it can't tell you how to fix them. You have to work that out for
yourself. But at least you have the information!
|
Author: njn
Date: 2009-07-30 03:57:52 +0100 (Thu, 30 Jul 2009)
New Revision: 10659
Log:
We currently use a mix of <option> and <computeroutput> tags for command
line options. This commit changes them to all <option>.
Also make consistent how options with multiple names (eg. -h --help) are
shown.
Also, remove section describing --help and --version in Callgrind's chapter;
these aren't necessary and are presumably a hangover from when Callgrind was
a separate tool.
Modified:
trunk/cachegrind/docs/cg-manual.xml
trunk/callgrind/docs/cl-manual.xml
trunk/callgrind/docs/man-annotate.xml
trunk/callgrind/docs/man-control.xml
trunk/docs/xml/manual-core-adv.xml
trunk/docs/xml/manual-core.xml
trunk/docs/xml/quick-start-guide.xml
trunk/docs/xml/xml_help.txt
trunk/drd/docs/drd-manual.xml
trunk/exp-bbv/docs/bbv-manual.xml
trunk/exp-ptrcheck/docs/pc-manual.xml
trunk/helgrind/docs/hg-manual.xml
trunk/lackey/docs/lk-manual.xml
trunk/massif/docs/ms-manual.xml
trunk/memcheck/docs/mc-manual.xml
trunk/memcheck/docs/mc-tech-docs.xml
trunk/none/docs/nl-manual.xml
Modified: trunk/cachegrind/docs/cg-manual.xml
===================================================================
--- trunk/cachegrind/docs/cg-manual.xml 2009-07-30 02:27:17 UTC (rev 10658)
+++ trunk/cachegrind/docs/cg-manual.xml 2009-07-30 02:57:52 UTC (rev 10659)
@@ -8,7 +8,7 @@
<title>Cachegrind: a cache and branch-prediction profiler</title>
<para>To use this tool, you must specify
-<computeroutput>--tool=cachegrind</computeroutput> on the
+<option>--tool=cachegrind</option> on the
Valgrind command line.</para>
<sect1 id="cg-manual.overview" xreflabel="Overview">
@@ -55,7 +55,7 @@
executed per line, which can be useful for traditional profiling.</para>
<para>Branch profiling is not enabled by default. To use it, you must
-additionally specify <computeroutput>--branch-sim=yes</computeroutput>
+additionally specify <option>--branch-sim=yes</option>
on the command line.</para>
@@ -64,7 +64,7 @@
<para>First off, as for normal Valgrind use, you probably want to
compile with debugging info (the
-<computeroutput>-g</computeroutput> flag). But by contrast with
+<option>-g</option> flag). But by contrast with
normal Valgrind use, you probably <command>do</command> want to turn
optimisation on, since you should profile your program as it will
be normally run.</para>
@@ -83,7 +83,7 @@
<para>Branch prediction statistics are not collected by default.
To do so, add the flag
- <computeroutput>--branch-sim=yes</computeroutput>.
+ <option>--branch-sim=yes</option>.
</para>
<para>This step should be done every time you want to collect
@@ -98,7 +98,7 @@
files to annotate can be specified manually, or manually on
the command line, or "interesting" source files can be
annotated automatically with the
- <computeroutput>--auto=yes</computeroutput> option. You can
+ <option>--auto=yes</option> option. You can
annotate C/C++ files or assembly language files equally
easily.</para>
@@ -175,9 +175,9 @@
of a model 3/4 Athlon). Cachegrind will tell you if this
happens. You can manually specify one, two or all three levels
(I1/D1/L2) of the cache from the command line using the
-<computeroutput>--I1</computeroutput>,
-<computeroutput>--D1</computeroutput> and
-<computeroutput>--L2</computeroutput> options.
+<option>--I1</option>,
+<option>--D1</option> and
+<option>--L2</option> options.
For cache parameters to be valid for simulation, the number
of sets (with associativity being the number of cache lines in
each set) has to be a power of two.</para>
@@ -186,9 +186,9 @@
Cachegrind cannot automatically
determine the cache configuration, so you will
need to specify it with the
-<computeroutput>--I1</computeroutput>,
-<computeroutput>--D1</computeroutput> and
-<computeroutput>--L2</computeroutput> options.</para>
+<option>--I1</option>,
+<option>--D1</option> and
+<option>--L2</option> options.</para>
<para>Other noteworthy behaviour:</para>
@@ -356,7 +356,7 @@
<listitem>
<para>To use an output file name other than the default
<computeroutput>cachegrind.out</computeroutput>,
- use the <computeroutput>--cachegrind-out-file</computeroutput>
+ use the <option>--cachegrind-out-file</option>
switch.</para>
</listitem>
<listitem>
@@ -371,7 +371,7 @@
on the output file name serves two purposes. Firstly, it means you
don't have to rename old log files that you don't want to overwrite.
Secondly, and more importantly, it allows correct profiling with the
-<computeroutput>--trace-children=yes</computeroutput> option of
+<option>--trace-children=yes</option> option of
programs that spawn child processes.</para>
</sect2>
@@ -465,8 +465,8 @@
<para>Enables or disables collection of branch instruction and
misprediction counts. By default this is disabled as it
slows Cachegrind down by approximately 25%. Note that you
- cannot specify <computeroutput>--cache-sim=no</computeroutput>
- and <computeroutput>--branch-sim=no</computeroutput>
+ cannot specify <option>--cache-sim=no</option>
+ and <option>--branch-sim=no</option>
together, as that would leave Cachegrind with no
information to collect.</para>
</listitem>
@@ -615,7 +615,7 @@
<listitem>
<para>Events shown: the events shown, which is a subset of the events
gathered. This can be adjusted with the
- <computeroutput>--show</computeroutput> option.</para>
+ <option>--show</option> option.</para>
</listitem>
<listitem>
@@ -626,12 +626,12 @@
<computeroutput>Ir</computeroutput> counts, they will then be
sorted by <computeroutput>I1mr</computeroutput> counts, and
so on. This order can be adjusted with the
- <computeroutput>--sort</computeroutput> option.</para>
+ <option>--sort</option> option.</para>
<para>Note that this dictates the order the functions appear.
It is <command>not</command> the order in which the columns
appear; that is dictated by the "events shown" line (and can
- be changed with the <computeroutput>--show</computeroutput>
+ be changed with the <option>--show</option>
option).</para>
</listitem>
@@ -644,7 +644,7 @@
<computeroutput>Ir</computeroutput> is chosen as the
threshold event since it is the primary sort event. The
threshold can be adjusted with the
- <computeroutput>--threshold</computeroutput>
+ <option>--threshold</option>
option.</para>
</listitem>
@@ -655,7 +655,7 @@
<listitem>
<para>Auto-annotation: whether auto-annotation was requested
- via the <computeroutput>--auto=yes</computeroutput>
+ via the <option>--auto=yes</option>
option. In this case no.</para>
</listitem>
@@ -676,7 +676,7 @@
and/or function name could not be determined from debugging
information. If most of the entries have the form
<computeroutput>???:???</computeroutput> the program probably
-wasn't compiled with <computeroutput>-g</computeroutput>. If any
+wasn't compiled with <option>-g</option>. If any
code was invalidated (either due to self-modifying code or
unloading of shared objects) its counts are aggregated into a
single cost centre written as
@@ -688,7 +688,7 @@
<para>There are two ways to annotate source files -- by choosing
them manually, or with the
-<computeroutput>--auto=yes</computeroutput> option. To do it
+<option>--auto=yes</option> option. To do it
manually, just specify the filenames as additional arguments to
cg_annotate. For example, the
output from running <filename>cg_annotate <filename>
@@ -736,7 +736,7 @@
(<computeroutput>User-annotated source</computeroutput>) as
having been chosen manually for annotation. If the file was
found in one of the directories specified with the
-<computeroutput>-I / --include</computeroutput> option, the directory
+<option>-I</option>/<option>--include</option> option, the directory
and file are both given.</para>
<para>Each line is annotated with its event counts. Events not
@@ -757,7 +757,7 @@
(figures and code for line 878)]]></programlisting>
<para>The amount of context to show around annotated lines is
-controlled by the <computeroutput>--context</computeroutput>
+controlled by the <option>--context</option>
option.</para>
<para>To get automatic annotation, run
@@ -765,8 +765,8 @@
cg_annotate will automatically annotate every source file it can
find that is mentioned in the function-by-function summary.
Therefore, the files chosen for auto-annotation are affected by
-the <computeroutput>--sort</computeroutput> and
-<computeroutput>--threshold</computeroutput> options. Each
+the <option>--sort</option> and
+<option>--threshold</option> options. Each
source file is clearly marked (<computeroutput>Auto-annotated
source</computeroutput>) as being chosen automatically. Any
files that could not be found are mentioned at the end of the
@@ -785,9 +785,9 @@
are often not present on a system. If a file is chosen for
annotation <command>both</command> manually and automatically, it
is marked as <computeroutput>User-annotated
-source</computeroutput>. Use the <computeroutput>-I /
---include</computeroutput> option to tell Valgrind where to look
-for source files if the filenames found from the debugging
+source</computeroutput>. Use the
+<option>-I</option>/<option>--include</option> option to tell Valgrind where
+to look for source files if the filenames found from the debugging
information aren't specific enough.</para>
<para>Beware that cg_annotate can take some time to digest large
@@ -839,27 +839,25 @@
<itemizedlist>
<listitem>
- <para><computeroutput>-h, --help</computeroutput></para>
- <para><computeroutput>-v, --version</computeroutput></para>
+ <para><option>-h --help</option></para>
+ <para><option>-v --version</option></para>
<para>Help and version, as usual.</para>
</listitem>
<listitem id="sort">
- <para><computeroutput>--sort=A,B,C</computeroutput> [default:
+ <para><option>--sort=A,B,C</option> [default:
order in
<computeroutput>cachegrind.out.<pid></computeroutput>]</para>
<para>Specifies the events upon which the sorting of the
function-by-function entries will be based. Useful if you
want to concentrate on eg. I cache misses
- (<computeroutput>--sort=I1mr,I2mr</computeroutput>), or D
- cache misses
- (<computeroutput>--sort=D1mr,D2mr</computeroutput>), or L2
- misses
- (<computeroutput>--sort=D2mr,I2mr</computeroutput>).</para>
+ (<option>--sort=I1mr,I2mr</option>), or D cache misses
+ (<option>--sort=D1mr,D2mr</option>), or L2 misses
+ (<option>--sort=D2mr,I2mr</option>).</para>
</listitem>
<listitem id="show">
- <para><computeroutput>--show=A,B,C</computeroutput> [default:
+ <para><option>--show=A,B,C</option> [default:
all, using order in
<computeroutput>cachegrind.out.<pid></computeroutput>]</para>
<para>Specifies which events to show (and the column
@@ -869,7 +867,7 @@
</listitem>
<listitem id="threshold">
- <para><computeroutput>--threshold=X</computeroutput>
+ <para><option>--threshold=X</option>
[default: 99%]</para>
<para>Sets the threshold for the function-by-function
summary. Functions are shown that account for more than X%
@@ -878,24 +876,23 @@
<para>Note: thresholds can be set for more than one of the
events by appending any events for the
- <computeroutput>--sort</computeroutput> option with a colon
+ <option>--sort</option> option with a colon
and a number (no spaces, though). E.g. if you want to see
the functions that cover 99% of L2 read misses and 99% of L2
write misses, use this option:</para>
- <para><computeroutput>--sort=D2mr:99,D2mw:99</computeroutput></para>
+ <para><option>--sort=D2mr:99,D2mw:99</option></para>
</listitem>
<listitem id="auto">
- <para><computeroutput>--auto=no</computeroutput> [default]</para>
- <para><computeroutput>--auto=yes</computeroutput></para>
+ <para><option>--auto=no</option> [default]</para>
+ <para><option>--auto=yes</option></para>
<para>When enabled, automatically annotates every file that
is mentioned in the function-by-function summary that can be
found. Also gives a list of those that couldn't be found.</para>
</listitem>
<listitem id="context">
- <para><computeroutput>--context=N</computeroutput> [default:
- 8]</para>
+ <para><option>--context=N</option> [default: 8]</para>
<para>Print N lines of context before and after each
annotated line. Avoids printing large sections of source
files that were not executed. Use a large number
@@ -903,9 +900,8 @@
</listitem>
<listitem id="include">
- <para><computeroutput>-I<dir>,
- --include=<dir></computeroutput> [default: empty
- string]</para>
+ <para><option>-I<dir>, --include=<dir></option>
+ [default: empty string]</para>
<para>Adds a directory to the list in which to search for
files. Multiple -I/--include options can be given to add
multiple directories.</para>
@@ -1046,7 +1042,7 @@
<listitem>
<para>If you compile some files with
- <computeroutput>-g</computeroutput> and some without, some
+ <option>-g</option> and some without, some
events that take place in a file without debug info could be
attributed to the last line of a file with debug info
(whichever one gets placed before the non-debug-info file in
Modified: trunk/callgrind/docs/cl-manual.xml
===================================================================
--- trunk/callgrind/docs/cl-manual.xml 2009-07-30 02:27:17 UTC (rev 10658)
+++ trunk/callgrind/docs/cl-manual.xml 2009-07-30 02:57:52 UTC (rev 10659)
@@ -8,7 +8,7 @@
<para>To use this tool, you must specify
-<computeroutput>--tool=callgrind</computeroutput> on the
+<option>--tool=callgrind</option> on the
Valgrind command line.</para>
<sect1 id="cl-manual.use" xreflabel="Overview">
@@ -61,7 +61,7 @@
</variablelist>
<para>To use Callgrind, you must specify
-<computeroutput>--tool=callgrind</computeroutput> on the Valgrind
+<option>--tool=callgrind</option> on the Valgrind
command line.</para>
<sect2 id="cl-manual.functionality" xreflabel="Functionality">
@@ -498,8 +498,7 @@
<title>Command line option reference</title>
<para>
-In the following, options are grouped into classes, in the same order as
-the output of <computeroutput>callgrind --help</computeroutput>.
+In the following, options are grouped into classes.
</para>
<para>
Some options allow the specification of a function/symbol name, such as
@@ -513,30 +512,6 @@
usage, the function would have to be specified in full extent, including
parameter signature. </para>
-<sect2 id="cl-manual.options.misc"
- xreflabel="Miscellaneous options">
-<title>Miscellaneous options</title>
-
-<variablelist id="cl.opts.list.misc">
-
- <varlistentry>
- <term><option>--help</option></term>
- <listitem>
- <para>Show summary of options. This is a short version of this
- manual section.</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><option>--version</option></term>
- <listitem>
- <para>Show version of callgrind.</para>
- </listitem>
- </varlistentry>
-
-</variablelist>
-</sect2>
-
<sect2 id="cl-manual.options.creation"
xreflabel="Dump creation options">
<title>Dump creation options</title>
@@ -750,9 +725,9 @@
option <xref linkend="opt.toggle-collect"/>. If you use this flag,
collection
state should be switched off at the beginning. Note that the
- specification of <computeroutput>--toggle-collect</computeroutput>
+ specification of <option>--toggle-collect</option>
implicitly sets
- <computeroutput>--collect-state=no</computeroutput>.</para>
+ <option>--collect-state=no</option>.</para>
<para>Collection state can be toggled also by inserting the client request
<computeroutput><xref linkend="cr.toggle-collect"/>;</computeroutput>
at the needed code positions.</para>
Modified: trunk/callgrind/docs/man-annotate.xml
===================================================================
--- trunk/callgrind/docs/man-annotate.xml 2009-07-30 02:27:17 UTC (rev 10658)
+++ trunk/callgrind/docs/man-annotate.xml 2009-07-30 02:57:52 UTC (rev 10659)
@@ -48,7 +48,7 @@
<variablelist remap="TP">
<varlistentry>
- <term><option>-h, --help</option></term>
+ <term><option>-h --help</option></term>
<listitem>
<para>Show summary of options.</para>
</listitem>
Modified: trunk/callgrind/docs/man-control.xml
===================================================================
--- trunk/callgrind/docs/man-control.xml 2009-07-30 02:27:17 UTC (rev 10658)
+++ trunk/callgrind/docs/man-control.xml 2009-07-30 02:57:52 UTC (rev 10659)
@@ -49,7 +49,7 @@
<variablelist remap="TP">
<varlistentry>
- <term><option>-h, --help</option></term>
+ <term><option>-h --help</option></term>
<listitem>
<para>Show summary of options.</para>
</listitem>
Modified: trunk/docs/xml/manual-core-adv.xml
===================================================================
--- trunk/docs/xml/manual-core-adv.xml 2009-07-30 02:27:17 UTC (rev 10658)
+++ trunk/docs/xml/manual-core-adv.xml 2009-07-30 02:57:52 UTC (rev 10659)
@@ -56,8 +56,8 @@
on x86, amd64, ppc32 and ppc64, the overhead is 6 simple integer instructions
and is probably undetectable except in tight loops.
However, if you really wish to compile out the client requests, you can
-compile with <computeroutput>-DNVALGRIND</computeroutput> (analogous to
-<computeroutput>-DNDEBUG</computeroutput>'s effect on
+compile with <option>-DNVALGRIND</option> (analogous to
+<option>-DNDEBUG</option>'s effect on
<computeroutput>assert()</computeroutput>).
</para>
@@ -103,7 +103,7 @@
once.</para>
<para>
Alternatively, for transparent self-modifying-code support,
- use<computeroutput>--smc-check=all</computeroutput>, or run
+ use<option>--smc-check=all</option>, or run
on ppc32/Linux or ppc64/Linux.
</para>
</listitem>
@@ -504,7 +504,7 @@
<para>Figuring out what's going on given the dynamic nature of wrapping
can be difficult. The
-<computeroutput>--trace-redir=yes</computeroutput> flag makes
+<option>--trace-redir=yes</option> flag makes
this possible
by showing the complete state of the redirection subsystem after
every
@@ -536,10 +536,10 @@
the specifications, and all known symbol names, following any change
to the specification set.</para>
-<para><computeroutput>--trace-redir=yes</computeroutput> shows the contents
+<para><option>--trace-redir=yes</option> shows the contents
of both sets following any such event.</para>
-<para><computeroutput>-v</computeroutput> prints a line of text each
+<para><option>-v</option> prints a line of text each
time an active specification is used for the first time.</para>
<para>Hence for maximum debugging effectiveness you will need to use both
@@ -555,7 +555,7 @@
of interception (wrapping vs replacement) are treated differently.
</para>
-<para><computeroutput>--trace-redir=yes</computeroutput> shows
+<para><option>--trace-redir=yes</option> shows
specifications and bindings for both
replacement and wrapper functions. To differentiate the
two, replacement bindings are printed using
Modified: trunk/docs/xml/manual-core.xml
===================================================================
--- trunk/docs/xml/manual-core.xml 2009-07-30 02:27:17 UTC (rev 10658)
+++ trunk/docs/xml/manual-core.xml 2009-07-30 02:57:52 UTC (rev 10659)
@@ -113,20 +113,20 @@
other debugger.</para>
<para>If you are planning to use Memcheck: On rare
-occasions, compiler optimisations (at <computeroutput>-O2</computeroutput>
-and above, and sometimes <computeroutput>-O1</computeroutput>) have been
+occasions, compiler optimisations (at <option>-O2</option>
+and above, and sometimes <option>-O1</option>) have been
observed to generate code which fools Memcheck into wrongly reporting
uninitialised value errors, or missing uninitialised value errors. We have
looked in detail into fixing this, and unfortunately the result is that
doing so would give a further significant slowdown in what is already a slow
tool. So the best solution is to turn off optimisation altogether. Since
this often makes things unmanageably slow, a reasonable compromise is to use
-<computeroutput>-O</computeroutput>. This gets you the majority of the
+<option>-O</option>. This gets you the majority of the
benefits of higher optimisation levels whilst keeping relatively small the
chances of false positives or false negatives from Memcheck. Also, you
-should compile your code with <computeroutput>-Wall</computeroutput> because
+should compile your code with <option>-Wall</option> because
it can identify some or all of the problems that Valgrind can miss at the
-higher optimisation levels. (Using <computeroutput>-Wall</computeroutput>
+higher optimisation levels. (Using <option>-Wall</option>
is also a good idea in general.) All other tools (as far as we know) are
unaffected by optimisation level.</para>
@@ -631,7 +631,7 @@
</varlistentry>
<varlistentry id="opt.quiet" xreflabel="--quiet">
- <term><option>-q --quiet</option></term>
+ <term><option>-q</option>, <option>--quiet</option></term>
<listitem>
<para>Run silently, and only print error messages. Useful if you
are running regression tests or have some other automated test
@@ -640,7 +640,7 @@
</varlistentry>
<varlistentry id="opt.verbose" xreflabel="--verbose">
- <term><option>-v --verbose</option></term>
+ <term><option>-v</option>, <option>--verbose</option></term>
<listitem>
<para>Be more verbose. Gives extra information on various aspects
of your program, such as: the shared objects loaded, the
@@ -1525,7 +1525,7 @@
run. Without the <computeroutput>memcheck:</computeroutput>
part, this will cause problems if you select other tools that
don't understand
-<computeroutput>--leak-check=yes</computeroutput>.</para>
+<option>--leak-check=yes</option>.</para>
</sect2>
@@ -1589,7 +1589,7 @@
<para>If you're using signals in clever ways (for example, catching
SIGSEGV, modifying page state and restarting the instruction), you're
probably relying on precise exceptions. In this case, you will need
-to use <computeroutput>--vex-iropt-precise-memory-exns=yes</computeroutput>.
+to use <option>--vex-iropt-precise-memory-exns=yes</option>.
</para>
<para>If your program dies as a result of a fatal core-dumping signal,
@@ -1961,7 +1961,7 @@
<title>Warning Messages You Might See</title>
<para>Most of these only appear if you run in verbose mode
-(enabled by <computeroutput>-v</computeroutput>):</para>
+(enabled by <option>-v</option>):</para>
<itemizedlist>
Modified: trunk/docs/xml/quick-start-guide.xml
===================================================================
--- trunk/docs/xml/quick-start-guide.xml 2009-07-30 02:27:17 UTC (rev 10658)
+++ trunk/docs/xml/quick-start-guide.xml 2009-07-30 02:57:52 UTC (rev 10659)
@@ -44,13 +44,13 @@
<para>Compile your program with <option>-g</option> to include debugging
information so that Memcheck's error messages include exact line
-numbers. Using <computeroutput>-O0</computeroutput> is also a good
+numbers. Using <option>-O0</option> is also a good
idea, if you can tolerate the slowdown. With
-<computeroutput>-O1</computeroutput> line numbers in error messages can
+<option>-O1</option> line numbers in error messages can
be inaccurate, although generally speaking running Memcheck on code compiled
-at <computeroutput>-O1</computeroutput> works fairly well.
+at <option>-O1</option> works fairly well.
Use of
-<computeroutput>-O2</computeroutput> and above is not recommended as
+<option>-O2</option> and above is not recommended as
Memcheck occasionally reports uninitialised-value errors which don't
really exist.</para>
Modified: trunk/docs/xml/xml_help.txt
===================================================================
--- trunk/docs/xml/xml_help.txt 2009-07-30 02:27:17 UTC (rev 10658)
+++ trunk/docs/xml/xml_help.txt 2009-07-30 02:57:52 UTC (rev 10659)
@@ -17,8 +17,12 @@
<programlisting> --> <pre class="programlisting">
<screen> --> <pre class="screen">
-<computeroutput> --> <tt class="computeroutput">
-<literal> --> <tt>
+<option> --> <code class="option">
+<filename> --> <code class="filename">
+<function> --> <code class="function">
+<literal> --> <code class="literal">
+<varname> --> <code class="varname">
+<computeroutput> --> <code class="computeroutput">
<emphasis> --> <i>
<command> --> <b class="command">
<blockquote> --> <div class="blockquote">
Modified: trunk/drd/docs/drd-manual.xml
===================================================================
--- trunk/drd/docs/drd-manual.xml 2009-07-30 02:27:17 UTC (rev 10658)
+++ trunk/drd/docs/drd-manual.xml 2009-07-30 02:57:52 UTC (rev 10659)
@@ -8,7 +8,7 @@
<title>DRD: a thread error detector</title>
<para>To use this tool, you must specify
-<computeroutput>--tool=drd</computeroutput>
+<option>--tool=drd</option>
on the Valgrind command line.</para>
@@ -653,7 +653,7 @@
displayed. For dynamically allocated data the allocation call
stack is shown. For static variables and stack variables the
allocation context is only shown when the option
- <computeroutput>--read-var-info=yes</computeroutput> has been
+ <option>--read-var-info=yes</option> has been
specified. Otherwise DRD will print <computeroutput>Allocation
context: unknown</computeroutput>.
</para>
Modified: trunk/exp-bbv/docs/bbv-manual.xml
===================================================================
--- trunk/exp-bbv/docs/bbv-manual.xml 2009-07-30 02:27:17 UTC (rev 10658)
+++ trunk/exp-bbv/docs/bbv-manual.xml 2009-07-30 02:57:52 UTC (rev 10659)
@@ -6,7 +6,7 @@
<title>BBV: an experimental basic block vector generation tool</title>
<para>To use this tool, you must specify
-<computeroutput>--tool=exp-bbv</computeroutput> on the Valgrind
+<option>--tool=exp-bbv</option> on the Valgrind
command line.</para>
<sect1 id="bbv-manual.overview" xreflabel="Overview">
@@ -202,7 +202,7 @@
<para>
The Basic Block Vector is dumped at fixed intervals. This
is commonly done every 100 million instructions; the
- <computeroutput>--interval-size</computeroutput> option can be
+ <option>--interval-size</option> option can be
used to change this.
</para>
@@ -252,7 +252,7 @@
BBV vectors will be different than those generated by other tools.
In practice this does not seem to affect the accuracy of the
SimPoint results. We do internally force the
- <computeroutput>--vex-guest-chase-thresh=0</computeroutput>
+ <option>--vex-guest-chase-thresh=0</option>
option to Valgrind which forces a more basic-block like
behavior.
</para>
Modified: trunk/exp-ptrcheck/docs/pc-manual.xml
===================================================================
--- trunk/exp-ptrcheck/docs/pc-manual.xml 2009-07-30 02:27:17 UTC (rev 10658)
+++ trunk/exp-ptrcheck/docs/pc-manual.xml 2009-07-30 02:57:52 UTC (rev 10659)
@@ -9,7 +9,7 @@
<title>Ptrcheck: an experimental heap, stack & global array overrun detector</title>
<para>To use this tool, you must specify
-<computeroutput>--tool=exp-ptrcheck</computeroutput> on the Valgrind
+<option>--tool=exp-ptrcheck</option> on the Valgrind
command line.</para>
@@ -161,7 +161,7 @@
<title>How Ptrcheck Works: Stack and Global Checks</title>
<para>When a source file is compiled
-with <computeroutput>-g</computeroutput>, the compiler attaches DWARF3
+with <option>-g</option>, the compiler attaches DWARF3
debugging information which describes the location of all stack and
global arrays in the file.</para>
Modified: trunk/helgrind/docs/hg-manual.xml
===================================================================
--- trunk/helgrind/docs/hg-manual.xml 2009-07-30 02:27:17 UTC (rev 10658)
+++ trunk/helgrind/docs/hg-manual.xml 2009-07-30 02:57:52 UTC (rev 10659)
@@ -8,7 +8,7 @@
<title>Helgrind: a thread error detector</title>
<para>To use this tool, you must specify
-<computeroutput>--tool=helgrind</computeroutput> on the Valgrind
+<option>--tool=helgrind</option> on the Valgrind
command line.</para>
Modified: trunk/lackey/docs/lk-manual.xml
===================================================================
--- trunk/lackey/docs/lk-manual.xml 2009-07-30 02:27:17 UTC (rev 10658)
+++ trunk/lackey/docs/lk-manual.xml 2009-07-30 02:57:52 UTC (rev 10659)
@@ -7,7 +7,7 @@
<title>Lackey: an example tool</title>
<para>To use this tool, you must specify
-<computeroutput>--tool=lackey</computeroutput> on the Valgrind
+<option>--tool=lackey</option> on the Valgrind
command line.</para>
@@ -26,7 +26,7 @@
<listitem>
<para>When command line option
- <computeroutput>--basic-counts=yes</computeroutput> is specified,
+ <option>--basic-counts=yes</option> is specified,
it prints the following statistics and information about the execution of
the client program:</para>
@@ -38,7 +38,7 @@
function in glibc's dynamic linker that resolves function
references to shared objects.</para>
<para>You can change the name of the function tracked with command line
- option <computeroutput>--fnname=<name></computeroutput>.</para>
+ option <option>--fnname=<name></option>.</para>
</listitem>
<listitem>
@@ -72,7 +72,7 @@
<listitem>
<para>When command line option
- <computeroutput>--detailed-counts=yes</computeroutput> is
+ <option>--detailed-counts=yes</option> is
specified, a table is printed with counts of loads, stores and ALU
operations for various types of operands.</para>
@@ -82,7 +82,7 @@
<listitem>
<para>When command line option
- <computeroutput>--trace-mem=yes</computeroutput> is
+ <option>--trace-mem=yes</option> is
specified, it prints out the size and address of almost every load and
store made by the program. See the comments at the top of the file
<computeroutput>lackey/lk_main.c</computeroutput> for details about
@@ -92,7 +92,7 @@
<listitem>
<para>When command line option
- <computeroutput>--trace-superblocks=yes</computeroutput> is
+ <option>--trace-superblocks=yes</option> is
specified, it prints out the address of every superblock
(extended basic block) executed by the program. This is
primarily of interest to Valgrind developers. See the comments at
@@ -104,14 +104,14 @@
</orderedlist>
<para>Note that Lackey runs quite slowly, especially when
-<computeroutput>--detailed-counts=yes</computeroutput> is specified.
+<option>--detailed-counts=yes</option> is specified.
It could be made to run a lot faster by doing a slightly more
sophisticated job of the instrumentation, but that would undermine
its role as a simple example tool. Hence we have chosen not to do
so.</para>
-<para>Note also that <computeroutput>--trace-mem=yes</computeroutput>
-and <computeroutput>--trace-superblocks=yes</computeroutput> create
+<para>Note also that <option>--trace-mem=yes</option>
+and <option>--trace-superblocks=yes</option> create
immense amounts of output. If you are saving the output in a file,
you can eat up tens of gigabytes of disk space very quickly.
As a result of printing out so much stuff, they also cause the program
Modified: trunk/massif/docs/ms-manual.xml
===================================================================
--- trunk/massif/docs/ms-manual.xml 2009-07-30 02:27:17 UTC (rev 10658)
+++ trunk/massif/docs/ms-manual.xml 2009-07-30 02:57:52 UTC (rev 10659)
@@ -8,7 +8,7 @@
<title>Massif: a heap profiler</title>
<para>To use this tool, you must specify
-<computeroutput>--tool=massif</computeroutput> on the Valgrind
+<option>--tool=massif</option> on the Valgrind
command line.</para>
<sect1 id="ms-manual.overview" xreflabel="Overview">
@@ -54,7 +54,7 @@
<para>First off, as for the other Valgrind tools, you should compile with
-debugging info (the <computeroutput>-g</computeroutput> flag). It shouldn't
+debugging info (the <option>-g</option> flag). It shouldn't
matter much what optimisation level you compile your program with, as this
is unlikely to affect the heap memory usage.</para>
@@ -188,7 +188,7 @@
instructions involve the loading and dynamic linking of the program. The
execution of <computeroutput>main</computeroutput> (and thus the heap
allocations) only occur at the very end. For a short-running program like
-this, we can use the <computeroutput>--time-unit=B</computeroutput> option
+this, we can use the <option>--time-unit=B</option> option
to specify that we want the time unit to instead be the number of bytes
allocated/deallocated on the heap and stack(s).</para>
@@ -232,7 +232,7 @@
runs for longer, it takes snapshots less frequently. It also discards older
snapshots as the program goes on; when it reaches the maximum number of
snapshots (100 by default, although changeable with the
-<computeroutput>--max-snapshots</computeroutput> option) half of them are
+<option>--max-snapshots</option> option) half of them are
deleted. This means that a reasonable number of snapshots are always
maintained.</para>
@@ -246,7 +246,7 @@
of '@' characters. The text at the bottom show that 3 detailed
snapshots were taken for this program (snapshots 9, 14 and 24). By default,
every 10th snapshot is detailed, although this can be changed via the
-<computeroutput>--detailed-freq</computeroutput> option.</para>
+<option>--detailed-freq</option> option.</para>
<para>Finally, there is at most one <emphasis>peak</emphasis> snapshot. The
peak snapshot is a detailed snapshot, and records the point where memory
@@ -260,7 +260,7 @@
the regular snapshots. However, recording the true peak is expensive, and
so by default Massif records a peak whose size is within 1% of the size of
the true peak. See the description of the
-<computeroutput>--peak-inaccuracy</computeroutput> option below for more
+<option>--peak-inaccuracy</option> option below for more
details.</para>
<para>The following graph is from an execution of Konqueror, the KDE web
@@ -331,7 +331,7 @@
<listitem><para>The time it was taken. In this case, the time unit is
bytes, due to the use of
- <computeroutput>--time-unit=B</computeroutput>.</para></listitem>
+ <option>--time-unit=B</option>.</para></listitem>
<listitem><para>The total memory consumption at that point.</para></listitem>
@@ -347,14 +347,14 @@
The exact number of administrative bytes depends on the details of the
allocator. By default Massif assumes 8 bytes per block, as can be seen
from the example, but this number can be changed via the
- <computeroutput>--heap-admin</computeroutput> option.</para>
+ <option>--heap-admin</option> option.</para>
<para>Second, allocators often round up the number of bytes asked for to a
larger number. By default, if N bytes are asked for, Massif rounds N up
to the nearest multiple of 8 that is equal to or greater than N. This is
typical behaviour for allocators, and is required to ensure that elements
within the block are suitably aligned. The rounding size can be changed
- with the <computeroutput>--alignment</computeroutput> option, although it
+ with the <option>--alignment</option> option, although it
cannot be less than 8, and must be a power of two.</para></listitem>
<listitem><para>The size of the stack(s). By default, stack profiling is
@@ -379,7 +379,7 @@
bytes) go through them. But how were <function>malloc</function> and new
called? At this point, every allocation so far has been due to line 21
inside <function>main</function>, hence the second line in the tree. The
-<computeroutput>-></computeroutput> indicates that main (line 20) called
+<option>-></option> indicates that main (line 20) called
<function>malloc</function>.</para>
<para>Let's see what the subsequent output shows happened next:</para>
@@ -491,7 +491,7 @@
The entries that do not meet this threshold are aggregated. This avoids
filling up the output with large numbers of unimportant entries. The
thresholds can be changed with the
-<computeroutput>--threshold</computeroutput> option that both Massif and
+<option>--threshold</option> option that both Massif and
ms_print support.</para>
</sect2>
@@ -617,7 +617,7 @@
<listitem>
<para>Any direct heap allocation (i.e. a call to
<function>malloc</function>, <function>new</function>, etc, or a call
- to a function name in a <computeroutput>--alloc-fn</computeroutput>
+ to a function name in a <option>--alloc-fn</option>
option) that occurs in a function specified by this option will be
ignored. This is mostly useful for testing purposes. This option can
be specified multiple times on the command line, to name multiple
@@ -632,7 +632,7 @@
</para>
<para>Note that overloaded C++ names must be written in full, as for
- <computeroutput>--alloc-fn</computeroutput> above.
+ <option>--alloc-fn</option> above.
</para>
</listitem>
</varlistentry>
@@ -685,7 +685,7 @@
</term>
<listitem>
<para>Frequency of detailed snapshots. With
- <computeroutput>--detailed-freq=1</computeroutput>, every snapshot is
+ <option>--detailed-freq=1</option>, every snapshot is
detailed.</para>
</listitem>
</varlistentry>
@@ -741,14 +741,14 @@
<itemizedlist>
<listitem>
- <para><computeroutput>-h, --help</computeroutput></para>
- <para><computeroutput>-v, --version</computeroutput></para>
+ <para><option>-h --help</option></para>
+ <para><option>-v --version</option></para>
<para>Help and version, as usual.</para>
</listitem>
<listitem>
<para><option><![CDATA[--threshold=<m.n>]]></option> [default: 1.0]</para>
- <para>Same as Massif's <computeroutput>--threshold</computeroutput>, but
+ <para>Same as Massif's <option>--threshold</option>, but
applied after profiling rather than during.</para>
</listitem>
Modified: trunk/memcheck/docs/mc-manual.xml
===================================================================
--- trunk/memcheck/docs/mc-manual.xml 2009-07-30 02:27:17 UTC (rev 10658)
+++ trunk/memcheck/docs/mc-manual.xml 2009-07-30 02:57:52 UTC (rev 10659)
@@ -157,7 +157,7 @@
lost" and "possibly lost" blocks. When enabled, the leak detector also
shows "reachable" and "indirectly lost" blocks. (In other words, it
shows all blocks, except suppressed ones, so
- <computeroutput>--show-all</computeroutput> would be a better name for
+ <option>--show-all</option> would be a better name for
it.)</para>
</listitem>
</varlistentry>
@@ -764,12 +764,12 @@
suppressed: 0 bytes in 0 blocks.
]]></programlisting>
-<para>If <computeroutput>--leak-check=full</computeroutput> is specified,
+<para>If <option>--leak-check=full</option> is specified,
Memcheck will give details for each definitely lost or possibly lost block,
including where it was allocated. (Actually, it merges results for all
blocks that have the same category and sufficiently similar stack traces
into a single "loss record". The
-<computeroutput>--leak-resolution</computeroutput> lets you control the
+<option>--leak-resolution</option> lets you control the
meaning of "sufficiently similar".) It cannot tell you when or how or why
the pointer to a leaked block was lost; you have to work that out for
yourself. In general, you should attempt to ensure your programs do not
@@ -795,7 +795,7 @@
The loss records are not presented in any notable order, so the loss record
numbers aren't particularly meaningful.</para>
-<para>If you specify <computeroutput>--show-reachable=yes</computeroutput>,
+<para>If you specify <option>--show-reachable=yes</option>,
reachable and indirectly lost blocks will also be shown, as the following
two examples show.</para>
@@ -1289,7 +1289,7 @@
<listitem>
<para><varname>VALGRIND_DO_LEAK_CHECK</varname>: does a full memory leak
- check (like <computeroutput>--leak-check=full</computeroutput> right now.
+ check (like <option>--leak-check=full</option> right now.
This is useful for incrementally checking for leaks between arbitrary
places in the program's execution. It has no return value.</para>
</listitem>
@@ -1297,7 +1297,7 @@
<listitem>
<para><varname>VALGRIND_DO_QUICK_LEAK_CHECK</varname>: like
<varname>VALGRIND_DO_LEAK_CHECK</varname>, except it produces only a leak
- summary (like <computeroutput>--leak-check=summary</computeroutput>).
+ summary (like <option>--leak-check=summary</option>).
It has no return value.</para>
</listitem>
@@ -1580,7 +1580,7 @@
MPI application you want to debug. By default, Valgrind tries
<computeroutput>mpicc</computeroutput>, but you can specify a
different one by using the configure-time flag
-<computeroutput>--with-mpicc=</computeroutput>. Currently the
+<option>--with-mpicc=</option>. Currently the
wrappers are only buildable with
<computeroutput>mpicc</computeroutput>s which are based on GNU
<computeroutput>gcc</computeroutput> or Intel's
@@ -1704,7 +1704,7 @@
</itemizedlist>
<para> If you want to use Valgrind's XML output facility
-(<computeroutput>--xml=yes</computeroutput>), you should pass
+(<option>--xml=yes</option>), you should pass
<computeroutput>quiet</computeroutput> in
<computeroutput>MPIWRAP_DEBUG</computeroutput> so as to get rid of any
extraneous printing from the wrappers.</para>
Modified: trunk/memcheck/docs/mc-tech-docs.xml
===================================================================
--- trunk/memcheck/docs/mc-tech-docs.xml 2009-07-30 02:27:17 UTC (rev 10658)
+++ trunk/memcheck/docs/mc-tech-docs.xml 2009-07-30 02:57:52 UTC (rev 10659)
@@ -87,7 +87,7 @@
support.</para>
<para><filename>valgrind.so</filename> is linked with the
-<computeroutput>-z initfirst</computeroutput> flag, which
+<option>-z initfirst</option> flag, which
requests that its initialisation code is run before that of any
other object in the executable image. When this happens,
valgrind gains control. The real CPU becomes "trapped" in
@@ -489,8 +489,8 @@
entirely.</para>
<para>To find out which glibc symbols are used by Valgrind,
- reinstate the link flags <computeroutput>-nostdlib
- -Wl,-no-undefined</computeroutput>. This causes linking to
+ reinstate the link flags <option>-nostdlib
+ -Wl,-no-undefined</option>. This causes linking to
fail, but will tell you what you depend on. I have mostly,
but not entirely, got rid of the glibc dependencies; what
remains is, IMO, fairly harmless. AFAIK the current
Modified: trunk/none/docs/nl-manual.xml
===================================================================
--- trunk/none/docs/nl-manual.xml 2009-07-30 02:27:17 UTC (rev 10658)
+++ trunk/none/docs/nl-manual.xml 2009-07-30 02:57:52 UTC (rev 10659)
@@ -8,7 +8,7 @@
<title>Nulgrind: the minimal Valgrind tool</title>
<para>To use this tool, you must specify
-<computeroutput>--tool=none</computeroutput> on the Valgrind
+<option>--tool=none</option> on the Valgrind
command line.</para>
<sect1 id="ms-manual.overview" xreflabel="Overview">
|
|
From: Tom H. <th...@cy...> - 2009-07-30 02:49:45
|
Nightly build on lloyd ( x86_64, Fedora 7 ) Started at 2009-07-30 03:05:05 BST Ended at 2009-07-30 03:49:20 BST 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 == 520 tests, 1 stderr failure, 0 stdout failures, 0 post failures == helgrind/tests/tc06_two_races_xml (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 == 519 tests, 1 stderr failure, 0 stdout failures, 0 post failures == helgrind/tests/tc06_two_races_xml (stderr) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Thu Jul 30 03:27:15 2009 --- new.short Thu Jul 30 03:49:20 2009 *************** *** 8,10 **** ! == 519 tests, 1 stderr failure, 0 stdout failures, 0 post failures == helgrind/tests/tc06_two_races_xml (stderr) --- 8,10 ---- ! == 520 tests, 1 stderr failure, 0 stdout failures, 0 post failures == helgrind/tests/tc06_two_races_xml (stderr) |
|
From: Tom H. <th...@cy...> - 2009-07-30 02:31:02
|
Nightly build on mg ( x86_64, Fedora 9 ) Started at 2009-07-30 03:10:03 BST Ended at 2009-07-30 03:30:41 BST 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 == 527 tests, 1 stderr failure, 0 stdout failures, 0 post failures == helgrind/tests/tc06_two_races_xml (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 == 526 tests, 1 stderr failure, 0 stdout failures, 0 post failures == helgrind/tests/tc06_two_races_xml (stderr) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Thu Jul 30 03:20:19 2009 --- new.short Thu Jul 30 03:30:41 2009 *************** *** 8,10 **** ! == 526 tests, 1 stderr failure, 0 stdout failures, 0 post failures == helgrind/tests/tc06_two_races_xml (stderr) --- 8,10 ---- ! == 527 tests, 1 stderr failure, 0 stdout failures, 0 post failures == helgrind/tests/tc06_two_races_xml (stderr) |
|
From: <sv...@va...> - 2009-07-30 02:27:41
|
Author: njn
Date: 2009-07-30 03:27:17 +0100 (Thu, 30 Jul 2009)
New Revision: 10658
Log:
Improve formatting of a command.
Modified:
trunk/exp-bbv/docs/bbv-manual.xml
Modified: trunk/exp-bbv/docs/bbv-manual.xml
===================================================================
--- trunk/exp-bbv/docs/bbv-manual.xml 2009-07-29 23:34:49 UTC (rev 10657)
+++ trunk/exp-bbv/docs/bbv-manual.xml 2009-07-30 02:27:17 UTC (rev 10658)
@@ -75,11 +75,12 @@
Assuming you have downloaded SimPoint 3.2 and compiled it,
create SimPoint results with a command like the following:
- <computeroutput>./SimPoint.3.2/bin/simpoint -inputVectorsGzipped \
- -loadFVFile bb.out.1234.gz \
- -k 5 -saveSimpoints results.simpts \
- -saveSimpointWeights results.weights
- </computeroutput>
+ <programlisting><![CDATA[
+./SimPoint.3.2/bin/simpoint -inputVectorsGzipped \
+ -loadFVFile bb.out.1234.gz \
+ -k 5 -saveSimpoints results.simpts \
+ -saveSimpointWeights results.weights]]></programlisting>
+
where bb.out.1234.gz is your compressed basic block vector file
generated by Valgrind exp-bbv.
</para>
|