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
(14) |
2
(16) |
3
(7) |
|
4
(7) |
5
(9) |
6
(8) |
7
(10) |
8
(16) |
9
(15) |
10
(9) |
|
11
(11) |
12
(13) |
13
(8) |
14
(8) |
15
(10) |
16
(25) |
17
(7) |
|
18
(7) |
19
(13) |
20
(10) |
21
(14) |
22
(11) |
23
(12) |
24
(8) |
|
25
(19) |
26
(10) |
27
(16) |
28
(13) |
|
|
|
|
From: Nicholas N. <nj...@cs...> - 2007-02-22 22:08:23
|
On Thu, 22 Feb 2007, Bart Van Assche wrote:
> There is the following comment in include/pub_tool_errormgr.h above
> VG_(maybe_record_error):
>
> The `extra' field can be stack-allocated; it will be copied by the
> core if needed (but it
> won't be copied if it's NULL).
>
> I do not understand this comment -- how can Valgrind's core copy the
> contents of the data the 'extra' pointer points at if it doesn't know
> the size of this data structure ? In the drd tool I allocate these
> 'extra' fields on the stack, but I'm afraid that this is the cause of
> the crash when starting the drd tool with Valgrind's command-line
> option -v.
The last sentence of the comment for the tool-defined 'update_extra'
function explains:
// Should fill in any details that could be postponed until after the
// decision whether to ignore the error (ie. details not affecting the
// result of VG_(tdict).tool_eq_Error()). This saves time when errors
// are ignored.
// Yuk.
// Return value: must be the size of the `extra' part in bytes -- used by
// the core to make a copy.
UInt (*update_extra)(Error* err),
The whole mechanism is ugly but I've never been able to think of a way to
improve it much.
Nick
|
|
From: Bart V. A. <bar...@gm...> - 2007-02-22 17:55:52
|
Hello,
While porting drd from X86 to AMD64 I noticed that all
multithreaded clients I ran under drd were terminated by a SIGSEGV
reported in std::locale::locale(). After some time I found a
workaround: insert the following statement in the pthread_mutex_lock()
wrapper (which does nothing except stopping statement reordering in
VEX):
write(1, "", 0);
When I saw this crash the first time I expected it to be a bug in drd.
But after I found the workaround I'm no longer sure it's a bug in drd
-- maybe it's a bug in VEX ? Details of how to reproduce the above
behavior can be found in http://bugs.kde.org/show_bug.cgi?id=142070.
--
Regards,
Bart Van Assche.
|
|
From: Bart V. A. <bar...@gm...> - 2007-02-22 17:40:31
|
There is the following comment in include/pub_tool_errormgr.h above VG_(maybe_record_error): The `extra' field can be stack-allocated; it will be copied by the core if needed (but it won't be copied if it's NULL). I do not understand this comment -- how can Valgrind's core copy the contents of the data the 'extra' pointer points at if it doesn't know the size of this data structure ? In the drd tool I allocate these 'extra' fields on the stack, but I'm afraid that this is the cause of the crash when starting the drd tool with Valgrind's command-line option -v. -- Regards, Bart Van Assche. |
|
From: Bart V. A. <bar...@gm...> - 2007-02-22 17:35:16
|
A new drd version is available at the following location: http://home.euphonynet.be/bvassche/valgrind/valgrind-6606-drd-2007-02-22.patch.gz Changes compared to version 2007-01-02: - Ported drd to AMD64 architecture -- drd now runs both on X86 and AMD64. More fine-tuning on AMD64 will be necessary however -- there are some false positives reported on AMD64 that are not reported on X86. - Eliminated false positives with regard to signal handling, and added a regression test. - Added two new client requests that allow to enable/disable recording of memory accesses on a per-thread bases. This was needed to suppress the false positives triggered by pthread_create() (which sets up the stack for another thread). - Extended drd's regression test stderr filter, to make regression tests run more reliably. Most important known bugs: - drd is soon killed by the OOM handler when started with bigger clients. - drd/default.supp has to be installed manually in the installation dir. - Valgrind option -v triggers a crash after the client program finished when drd has reported one or more errors in the client. -- Regards, Bart Van Assche. |
|
From: <js...@ac...> - 2007-02-22 09:46:02
|
Nightly build on minnie ( SuSE 10.0, ppc32 ) started at 2007-02-22 09:00:01 GMT Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 219 tests, 10 stderr failures, 6 stdout failures, 0 posttest failures == memcheck/tests/leak-tree (stderr) memcheck/tests/leakotron (stdout) memcheck/tests/pointer-trace (stderr) memcheck/tests/stack_changes (stderr) memcheck/tests/xml1 (stderr) none/tests/faultstatus (stderr) none/tests/fdleak_cmsg (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) none/tests/ppc32/jm-fp (stdout) none/tests/ppc32/jm-fp (stderr) none/tests/ppc32/round (stdout) none/tests/ppc32/round (stderr) none/tests/ppc32/test_fx (stdout) none/tests/ppc32/test_fx (stderr) none/tests/ppc32/test_gx (stdout) |
|
From: <js...@ac...> - 2007-02-22 05:30:09
|
Nightly build on phoenix ( SuSE 10.0 ) started at 2007-02-22 04:55:01 GMT Checking out vex source tree ... done Building vex ... done Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 254 tests, 6 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/leak-tree (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/scalar_supp (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) |
|
From: Tom H. <th...@cy...> - 2007-02-22 03:24:25
|
Nightly build on dellow ( x86_64, Fedora Core 6 ) started at 2007-02-22 03:10:09 GMT Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 288 tests, 4 stderr failures, 2 stdout failures, 0 posttest failures == memcheck/tests/pointer-trace (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/xml1 (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) none/tests/pth_detached (stdout) |
|
From: Tom H. <th...@cy...> - 2007-02-22 03:23:24
|
Nightly build on alvis ( i686, Red Hat 7.3 ) started at 2007-02-22 03:15:02 GMT Results differ from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Last 20 lines of verbose log follow echo /tmp/ccHXLKnx.s:4393: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccHXLKnx.s:4513: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccHXLKnx.s:4633: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccHXLKnx.s:4753: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccHXLKnx.s:4873: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccHXLKnx.s:4993: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccHXLKnx.s:5113: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccHXLKnx.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.12387/valgrind/none/tests/x86' make[4]: *** [check-am] Error 2 make[4]: Leaving directory `/tmp/valgrind.12387/valgrind/none/tests/x86' make[3]: *** [check-recursive] Error 1 make[3]: Leaving directory `/tmp/valgrind.12387/valgrind/none/tests' make[2]: *** [check-recursive] Error 1 make[2]: Leaving directory `/tmp/valgrind.12387/valgrind/none' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/tmp/valgrind.12387/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/ccwDEEbZ.s:4393: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccwDEEbZ.s:4513: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccwDEEbZ.s:4633: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccwDEEbZ.s:4753: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccwDEEbZ.s:4873: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccwDEEbZ.s:4993: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccwDEEbZ.s:5113: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccwDEEbZ.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.12387/valgrind/none/tests/x86' make[4]: *** [check-am] Error 2 make[4]: Leaving directory `/tmp/valgrind.12387/valgrind/none/tests/x86' make[3]: *** [check-recursive] Error 1 make[3]: Leaving directory `/tmp/valgrind.12387/valgrind/none/tests' make[2]: *** [check-recursive] Error 1 make[2]: Leaving directory `/tmp/valgrind.12387/valgrind/none' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/tmp/valgrind.12387/valgrind' make: *** [check] Error 2 ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Thu Feb 22 03:19:09 2007 --- new.short Thu Feb 22 03:23:17 2007 *************** *** 7,16 **** Last 20 lines of verbose log follow echo ! /tmp/ccwDEEbZ.s:4393: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccwDEEbZ.s:4513: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccwDEEbZ.s:4633: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccwDEEbZ.s:4753: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccwDEEbZ.s:4873: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccwDEEbZ.s:4993: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccwDEEbZ.s:5113: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccwDEEbZ.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/ccHXLKnx.s:4393: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccHXLKnx.s:4513: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccHXLKnx.s:4633: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccHXLKnx.s:4753: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccHXLKnx.s:4873: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccHXLKnx.s:4993: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccHXLKnx.s:5113: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccHXLKnx.s:5233: Error: no such instruction: `fisttpq -56(%ebp)' make[5]: *** [insn_sse3.o] Error 1 |
|
From: Tom H. <th...@cy...> - 2007-02-22 03:19:08
|
Nightly build on lloyd ( x86_64, Fedora Core 3 ) started at 2007-02-22 03:05:15 GMT Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 288 tests, 6 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/pointer-trace (stderr) memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/scalar_supp (stderr) memcheck/tests/xml1 (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) |
|
From: Tom H. <th...@cy...> - 2007-02-22 03:14:30
|
Nightly build on gill ( x86_64, Fedora Core 2 ) started at 2007-02-22 03:00:02 GMT Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 290 tests, 6 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/pointer-trace (stderr) memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/scalar_supp (stderr) none/tests/fdleak_fcntl (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) |
|
From: <js...@ac...> - 2007-02-22 01:09:22
|
Nightly build on g5 ( SuSE 10.1, ppc970 ) started at 2007-02-22 02:00:01 CET Results differ from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 225 tests, 6 stderr failures, 2 stdout failures, 0 posttest failures == memcheck/tests/deep_templates (stdout) memcheck/tests/leak-cycle (stderr) memcheck/tests/leak-tree (stderr) memcheck/tests/pointer-trace (stderr) none/tests/faultstatus (stderr) none/tests/fdleak_cmsg (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) ================================================= == Results from 24 hours ago == ================================================= Checking out valgrind source tree ... failed Last 20 lines of verbose log follow echo Checking out valgrind source tree ... svn co svn://svn.valgrind.org/valgrind/trunk -r {2007-02-21T02:00:01} valgrind svn: Unknown hostname 'svn.valgrind.org' ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Thu Feb 22 02:00:47 2007 --- new.short Thu Feb 22 02:09:19 2007 *************** *** 1,7 **** ! Checking out valgrind source tree ... failed ! Last 20 lines of verbose log follow echo - Checking out valgrind source tree ... svn co svn://svn.valgrind.org/valgrind/trunk -r {2007-02-21T02:00:01} valgrind - svn: Unknown hostname 'svn.valgrind.org' --- 1,18 ---- ! Checking out valgrind source tree ... done ! Configuring valgrind ... done ! Building valgrind ... done ! Running regression tests ... failed ! Regression test results follow ! ! == 225 tests, 6 stderr failures, 2 stdout failures, 0 posttest failures == ! memcheck/tests/deep_templates (stdout) ! memcheck/tests/leak-cycle (stderr) ! memcheck/tests/leak-tree (stderr) ! memcheck/tests/pointer-trace (stderr) ! none/tests/faultstatus (stderr) ! none/tests/fdleak_cmsg (stderr) ! none/tests/mremap (stderr) ! none/tests/mremap2 (stdout) |