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
(4) |
2
(3) |
3
(7) |
4
(7) |
5
(6) |
6
(5) |
|
7
(21) |
8
(14) |
9
(8) |
10
(10) |
11
(7) |
12
(4) |
13
|
|
14
(3) |
15
(11) |
16
(4) |
17
|
18
|
19
|
20
|
|
21
(3) |
22
(4) |
23
(2) |
24
(3) |
25
|
26
(4) |
27
(2) |
|
28
(6) |
29
|
30
(2) |
31
(7) |
|
|
|
|
From: Alexander P. <gl...@go...> - 2010-03-15 11:13:06
|
> root@bee:/# valgrind.bin --help Oh, I've missed your command line. This should have nothing to do with the ld.so or any code executed under Valgrind, it's possibly the Valgrind binary itself. How about dumping the list of instructions used by the binary (objdump -d valgrind) and making a test that uses them? Alex |
|
From: Alexander P. <gl...@go...> - 2010-03-15 11:04:00
|
Sorry, I'm running V on a real ARM CPU and can't help with running QEMU. Maybe the emulator just doesn't let Valgrind know about the SIGILL thus making it impossible to print the report. For the particular bug I've pointed to above you can try to break on __kernel_dmb (0xffff0fa0) and see if the program reaches this breakpoint running natively (i.e. without Valgrind) On Mon, Mar 15, 2010 at 1:56 PM, Loïc Minier <lo...@do...> wrote: > On Mon, Mar 15, 2010, Alexander Potapenko wrote: >> Unfortunately the bug report lacks the full log of Valgrind's run, >> especially the bytes containing the unhandled instruction, so it's >> hard to tell what causes the problem. > > I'm afraid it SIGILLs on the startup of valgrind itself: > root@bee:/# valgrind.bin --help > qemu: uncaught target signal 4 (Illegal instruction) - core dumped > Illegal instruction (core dumped) > > (that's under qemu syscall emulation, but it's the same under qemu > system emulation) > > Is there a way to get a longer log? > > Thanks for the details of ARM support, > -- > Loďc Minier > -- Alexander Potapenko Software Engineer Google Moscow |
|
From: Loïc M. <lo...@do...> - 2010-03-15 10:56:47
|
On Mon, Mar 15, 2010, Alexander Potapenko wrote: > Unfortunately the bug report lacks the full log of Valgrind's run, > especially the bytes containing the unhandled instruction, so it's > hard to tell what causes the problem. I'm afraid it SIGILLs on the startup of valgrind itself: root@bee:/# valgrind.bin --help qemu: uncaught target signal 4 (Illegal instruction) - core dumped Illegal instruction (core dumped) (that's under qemu syscall emulation, but it's the same under qemu system emulation) Is there a way to get a longer log? Thanks for the details of ARM support, -- Loïc Minier |
|
From: Alexander P. <gl...@go...> - 2010-03-15 10:33:40
|
Unfortunately the bug report lacks the full log of Valgrind's run, especially the bytes containing the unhandled instruction, so it's hard to tell what causes the problem. In fact Valgrind doesn't claim to support the full ARMv7 (even v6) instruction set, so you may experience problems with the tests using those. For example, newer systems tend to use the userspace memory barriers, which are not supported by Valgrind yet, within ld.so (see https://bugs.kde.org/show_bug.cgi?id=228060). Personally I've had problems with those running ld.so version 2.10.1 on the 2.6.31 kernel, whereas ld.so v. 2.9 and kernel 2.6.29 seemed to work ok. On Mon, Mar 15, 2010 at 12:27 PM, Loïc Minier <lo...@do...> wrote: > Hi folks > > valgrind recently got ported to ARM (nice work!), and it *builds* fine > on Ubuntu 10.04: > https://launchpad.net/ubuntu/+source/valgrind/1:3.6.0~svn20100212-0ubuntu3/+build/1562251 > > sadly, it's unusable as it SIGILLs in _start() on startup: > https://bugs.launchpad.net/ubuntu/+source/valgrind/+bug/537458 > > I suspect the very early init code needs porting to Thumb(-2); perhaps > the valgrind code needs a bunch of fixes to run Thumb(-2) binaries? > (We default to ARMv7 in Thumb-2 mode in Ubuntu 10.04). > > Is this in the works, or should we consider removing it from Ubuntu on > armel for this release and look back next cycle? > > Thanks! > -- > Loïc Minier > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Valgrind-developers mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-developers > -- Alexander Potapenko Software Engineer Google Moscow |
|
From: Loïc M. <lo...@do...> - 2010-03-15 09:50:42
|
Hi folks
valgrind recently got ported to ARM (nice work!), and it *builds* fine
on Ubuntu 10.04:
https://launchpad.net/ubuntu/+source/valgrind/1:3.6.0~svn20100212-0ubuntu3/+build/1562251
sadly, it's unusable as it SIGILLs in _start() on startup:
https://bugs.launchpad.net/ubuntu/+source/valgrind/+bug/537458
I suspect the very early init code needs porting to Thumb(-2); perhaps
the valgrind code needs a bunch of fixes to run Thumb(-2) binaries?
(We default to ARMv7 in Thumb-2 mode in Ubuntu 10.04).
Is this in the works, or should we consider removing it from Ubuntu on
armel for this release and look back next cycle?
Thanks!
--
Loïc Minier
|
|
From: <sv...@va...> - 2010-03-15 09:03:54
|
Author: sewardj
Date: 2010-03-15 09:03:25 +0000 (Mon, 15 Mar 2010)
New Revision: 11094
Log:
Fix stupid bug in VG_(bzero_inline), as spotted by Bart.
Modified:
trunk/include/pub_tool_libcbase.h
Modified: trunk/include/pub_tool_libcbase.h
===================================================================
--- trunk/include/pub_tool_libcbase.h 2010-03-14 17:19:02 UTC (rev 11093)
+++ trunk/include/pub_tool_libcbase.h 2010-03-15 09:03:25 UTC (rev 11094)
@@ -131,7 +131,7 @@
case 4: p[0] = p[1] = p[2] = p[3] = 0UL; return;
case 3: p[0] = p[1] = p[2] = 0UL; return;
case 2: p[0] = p[1] = 0UL; return;
- case 1: p[0] = 1; return;
+ case 1: p[0] = 0UL; return;
case 0: return;
default: break;
}
|
|
From: Julian S. <js...@ac...> - 2010-03-15 09:01:56
|
On Monday 15 March 2010, Bart Van Assche wrote: > In the above I see "p[0] = 1" for case 0. Is that correct ? Err, no! Thanks for spotting that. J |
|
From: Bart V. A. <bar...@gm...> - 2010-03-15 07:22:21
|
Nightly build on cellbuzz-native ( cellbuzz, ppc64, Fedora 7, native ) Started at 2010-03-15 02:00:05 EDT Ended at 2010-03-15 03:22:02 EDT Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... done Regression test results follow == 452 tests, 43 stderr failures, 10 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/linux/timerfd-syscall (stdout) memcheck/tests/linux-syscalls-2007 (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 (stdout) 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_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) |
|
From: Bart V. A. <bva...@ac...> - 2010-03-15 07:11:55
|
On Sun, Mar 14, 2010 at 6:19 PM, <sv...@va...> wrote:
>
> Author: sewardj
> Date: 2010-03-14 17:19:02 +0000 (Sun, 14 Mar 2010)
> New Revision: 11093
>
> Log:
> Inline most functions in VG_(use_CF_info). May or may not give a
> 3% performance increase for Helgrind in default (detailed-history)
> mode.
[ ... ]
> +/* Zero out up to 8 words quickly in-line. Do not use this for blocks
> + of size which are unknown at compile time, since the whole point is
> + for it to be inlined, and then for gcc to remove all code except
> + for the relevant 'sz' case. */
> +inline __attribute__((always_inline))
> +static void VG_(bzero_inline) ( void* s, SizeT sz )
> +{
> + if (LIKELY(0 == (((Addr)sz) & (Addr)(sizeof(UWord)-1)))
> + && LIKELY(0 == (((Addr)s) & (Addr)(sizeof(UWord)-1)))) {
> + UWord* p = (UWord*)s;
> + switch (sz / (SizeT)sizeof(UWord)) {
> + case 8: p[0] = p[1] = p[2] = p[3]
> + = p[4] = p[5] = p[6] = p[7] = 0UL; return;
> + case 7: p[0] = p[1] = p[2] = p[3]
> + = p[4] = p[5] = p[6] = 0UL; return;
> + case 6: p[0] = p[1] = p[2] = p[3]
> + = p[4] = p[5] = 0UL; return;
> + case 5: p[0] = p[1] = p[2] = p[3] = p[4] = 0UL; return;
> + case 4: p[0] = p[1] = p[2] = p[3] = 0UL; return;
> + case 3: p[0] = p[1] = p[2] = 0UL; return;
> + case 2: p[0] = p[1] = 0UL; return;
> + case 1: p[0] = 1; return;
> + case 0: return;
> + default: break;
> + }
> + }
> + VG_(memset)(s, 0, sz);
> +}
Hello Julian,
In the above I see "p[0] = 1" for case 0. Is that correct ?
Bart.
|
|
From: Tom H. <th...@cy...> - 2010-03-15 03:46:20
|
Nightly build on lloyd ( x86_64, Fedora 7 ) Started at 2010-03-15 03:05:03 GMT Ended at 2010-03-15 03:45:56 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 == 534 tests, 1 stderr failure, 0 stdout failures, 0 post failures == helgrind/tests/tc06_two_races_xml (stderr) |
|
From: Tom H. <th...@cy...> - 2010-03-15 03:36:59
|
Nightly build on mg ( x86_64, Fedora 9 ) Started at 2010-03-15 03:10:05 GMT Ended at 2010-03-15 03:36:41 GMT Results differ from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 541 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 == 541 tests, 2 stderr failures, 0 stdout failures, 0 post failures == helgrind/tests/pth_spinlock (stderr) helgrind/tests/tc06_two_races_xml (stderr) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Mon Mar 15 03:23:31 2010 --- new.short Mon Mar 15 03:36:41 2010 *************** *** 8,11 **** ! == 541 tests, 2 stderr failures, 0 stdout failures, 0 post failures == ! helgrind/tests/pth_spinlock (stderr) helgrind/tests/tc06_two_races_xml (stderr) --- 8,10 ---- ! == 541 tests, 1 stderr failure, 0 stdout failures, 0 post failures == helgrind/tests/tc06_two_races_xml (stderr) |