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
(11) |
2
(9) |
3
(11) |
4
(12) |
5
(11) |
|
6
(9) |
7
(13) |
8
(6) |
9
(7) |
10
(7) |
11
(11) |
12
(13) |
|
13
(7) |
14
(6) |
15
(7) |
16
(19) |
17
(20) |
18
(9) |
19
(9) |
|
20
(6) |
21
(7) |
22
(11) |
23
(16) |
24
(14) |
25
(24) |
26
(16) |
|
27
(20) |
28
(58) |
29
(7) |
30
(10) |
31
(15) |
|
|
|
From: Bart V. A. <bar...@gm...> - 2006-08-10 15:46:22
|
Hello,
Regarding the drd (data-race detection) tool I'm working on: I
have a question about how to obtain the name of a stack variable,
given its address.
Below there is an example of how the drd tool currently reports
data races. The information it reports is as follows, for each two
conflicting segments:
- Stack trace of the first instruction of the first segment.
- Stack trace of the first instruction of the second segment.
- A list of address ranges for which a race has been detected.
In order for this output to be useful, the user must be able to
correlate the output to the program text. This means reporting only
the addresses of conflicting data accesses is not enough. For static
variables I could obtain the variable name via VG_(find_seginfo)() and
VG_(seginfo_syms_getidx)(). For dynamically allocated variables I can
record the stack trace at the time malloc() is called. But how to
convert the address of a stack variable into the name of a variable ?
$ VALGRIND_LIB=.in_place coregrind/valgrind --tool=drd drd/tests/fp_race
...
==5449== Examining thread 2 (vc [ 1: 3, 2: 1 ]) versus thread 1 (vc [
1: 4 ]) 0 0
==5449== Thread 2:
==5449== 1st segment start
==5449== at: 0x4216648: clone (in /lib/libc-2.4.so)
==5449==
==5449== Thread 1:
==5449== 2nd segment start
==5449== at: 0x4216648: clone (in /lib/libc-2.4.so)
==5449== by: 0x403E9BD: pthread_create@@GLIBC_2.1 (in /lib/libpthread-2.4.so)
==5449== by: 0x401C8AA: pthread_create@* (vg_preloaded.c:116)
==5449== by: 0x804867B: main (fp_race.cpp:67)
==5449== by: 0x416E87C: (below main) (in /lib/libc-2.4.so)
==5449== by: 0x8048511: (within
/home/bart/software/valgrind-svn/drd/tests/fp_race)
==5449== 0x0401B310 sz 4 W W (segment ld-linux.so.2, symbol
_rtld_local @ 0x401B020 size 1524)
==5449== 0x0403817D sz 1 R W (heap)
==5449== 0x04A7BD9C sz 4 R W (stack with VG thread ID 2; kernel thread
ID 5450; POSIX thread ID 78101408)
==5449== 0x08049A08 sz 8 W W (segment NONE, symbol s_d3 @ 0x8049A08 size 8)
==5449== 0xBEC41FD4 sz 8 R W (stack with VG thread ID 1; kernel thread
ID 5449; POSIX thread ID 69704976)
--
Regards,
Bart Van Assche.
|
|
From: Nicholas N. <nj...@cs...> - 2006-08-10 11:44:31
|
On Thu, 10 Aug 2006, Bart Van Assche wrote: > Anyone any idea where I can find documentation on recursive invocation of > valgrind, if this is supported ? I started working again on my drd > (data-race detection) tool, and would like to test it with memcheck. Is this > possible ? Partly. README_DEVELOPERS has details on how to do this (under "Self-hosting"). Unfortunately using Memcheck on another tool won't give you useful results, because we haven't added the necessary client requests to tell Memcheck about all the nasty things Valgrind does with memory. So you'll get lots of false positives. Cachegrind works, however; that's how we got some of the speedups in 3.2.0. Nick |
|
From: Bart V. A. <bar...@gm...> - 2006-08-10 11:38:24
|
Anyone any idea where I can find documentation on recursive invocation of valgrind, if this is supported ? I started working again on my drd (data-race detection) tool, and would like to test it with memcheck. Is this possible ? When I download and build the latest valgrind sources, I get the following error message when I try to invoke valgrind on itself: $ VALGRIND_LIB=.in_place coregrind/valgrind --tool=memcheck coregrind/valgrind --tool=none drd/tests/fp_race ==17942== Memcheck, a memory error detector. ==17942== Copyright (C) 2002-2006, and GNU GPL'd, by Julian Seward et al. ==17942== Using LibVEX rev 1636, a library for dynamic binary translation. ==17942== Copyright (C) 2004-2006, and GNU GPL'd, by OpenWorks LLP. ==17942== Using valgrind-3.3.0.SVN, a dynamic binary instrumentation framework. ==17942== Copyright (C) 2000-2006, and GNU GPL'd, by Julian Seward et al. ==17942== For more details, rerun with: -v ==17942== valgrind: You cannot run 'coregrind/valgrind' directly. valgrind: You should use $prefix/bin/valgrind. |
|
From: Tom H. <th...@cy...> - 2006-08-10 06:33:25
|
Nightly build on gill ( x86_64, Fedora Core 2 ) started at 2006-08-10 03:00:16 BST Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 262 tests, 5 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/mempool (stderr) memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/scalar_supp (stderr) none/tests/fdleak_fcntl (stderr) none/tests/tls (stdout) |
|
From: Tom H. <to...@co...> - 2006-08-10 02:45:07
|
Nightly build on dunsmere ( athlon, Fedora Core 5 ) started at 2006-08-10 03:30:04 BST Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 237 tests, 4 stderr failures, 0 stdout failures, 0 posttest failures == memcheck/tests/pointer-trace (stderr) memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/xml1 (stderr) |
|
From: Tom H. <th...@cy...> - 2006-08-10 02:27:06
|
Nightly build on dellow ( x86_64, Fedora Core 5 ) started at 2006-08-10 03:10:07 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 == 260 tests, 3 stderr failures, 0 stdout failures, 0 posttest failures == memcheck/tests/mempool (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/xml1 (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 == 260 tests, 3 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/mempool (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/xml1 (stderr) none/tests/pth_cvsimple (stdout) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Thu Aug 10 03:18:31 2006 --- new.short Thu Aug 10 03:27:02 2006 *************** *** 8,10 **** ! == 260 tests, 3 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/mempool (stderr) --- 8,10 ---- ! == 260 tests, 3 stderr failures, 0 stdout failures, 0 posttest failures == memcheck/tests/mempool (stderr) *************** *** 12,14 **** memcheck/tests/xml1 (stderr) - none/tests/pth_cvsimple (stdout) --- 12,13 ---- |
|
From: Tom H. <th...@cy...> - 2006-08-10 02:26:41
|
Nightly build on alvis ( i686, Red Hat 7.3 ) started at 2006-08-10 03:15:02 BST Results differ from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Last 20 lines of verbose log follow echo /tmp/ccUhrDVA.s:4393: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccUhrDVA.s:4513: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccUhrDVA.s:4633: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccUhrDVA.s:4753: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccUhrDVA.s:4873: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccUhrDVA.s:4993: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccUhrDVA.s:5113: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccUhrDVA.s:5233: Error: no such instruction: `fisttpq -56(%ebp)' make[5]: *** [insn_sse3.o] Error 1 rm insn_mmx.c insn_sse2.c insn_fpu.c insn_mmxext.c insn_sse.c insn_sse3.c insn_cmov.c insn_basic.c make[5]: Leaving directory `/tmp/valgrind.20125/valgrind/none/tests/x86' make[4]: *** [check-am] Error 2 make[4]: Leaving directory `/tmp/valgrind.20125/valgrind/none/tests/x86' make[3]: *** [check-recursive] Error 1 make[3]: Leaving directory `/tmp/valgrind.20125/valgrind/none/tests' make[2]: *** [check-recursive] Error 1 make[2]: Leaving directory `/tmp/valgrind.20125/valgrind/none' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/tmp/valgrind.20125/valgrind' make: *** [check] Error 2 ================================================= == Results from 24 hours ago == ================================================= Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Last 20 lines of verbose log follow echo /tmp/ccw6ekrD.s:4393: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccw6ekrD.s:4513: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccw6ekrD.s:4633: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccw6ekrD.s:4753: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccw6ekrD.s:4873: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccw6ekrD.s:4993: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccw6ekrD.s:5113: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccw6ekrD.s:5233: Error: no such instruction: `fisttpq -56(%ebp)' make[5]: *** [insn_sse3.o] Error 1 rm insn_mmx.c insn_sse2.c insn_fpu.c insn_mmxext.c insn_sse.c insn_sse3.c insn_cmov.c insn_basic.c make[5]: Leaving directory `/tmp/valgrind.20125/valgrind/none/tests/x86' make[4]: *** [check-am] Error 2 make[4]: Leaving directory `/tmp/valgrind.20125/valgrind/none/tests/x86' make[3]: *** [check-recursive] Error 1 make[3]: Leaving directory `/tmp/valgrind.20125/valgrind/none/tests' make[2]: *** [check-recursive] Error 1 make[2]: Leaving directory `/tmp/valgrind.20125/valgrind/none' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/tmp/valgrind.20125/valgrind' make: *** [check] Error 2 ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Thu Aug 10 03:20:10 2006 --- new.short Thu Aug 10 03:26:33 2006 *************** *** 7,16 **** Last 20 lines of verbose log follow echo ! /tmp/ccw6ekrD.s:4393: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccw6ekrD.s:4513: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccw6ekrD.s:4633: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccw6ekrD.s:4753: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccw6ekrD.s:4873: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccw6ekrD.s:4993: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccw6ekrD.s:5113: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccw6ekrD.s:5233: Error: no such instruction: `fisttpq -56(%ebp)' make[5]: *** [insn_sse3.o] Error 1 --- 7,16 ---- Last 20 lines of verbose log follow echo ! /tmp/ccUhrDVA.s:4393: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccUhrDVA.s:4513: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccUhrDVA.s:4633: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccUhrDVA.s:4753: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccUhrDVA.s:4873: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccUhrDVA.s:4993: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccUhrDVA.s:5113: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccUhrDVA.s:5233: Error: no such instruction: `fisttpq -56(%ebp)' make[5]: *** [insn_sse3.o] Error 1 |