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
(15) |
2
(13) |
3
(16) |
4
(12) |
5
(17) |
|
6
(16) |
7
(13) |
8
(15) |
9
(15) |
10
(18) |
11
(5) |
12
(17) |
|
13
(13) |
14
(13) |
15
(5) |
16
(13) |
17
(2) |
18
(19) |
19
(12) |
|
20
|
21
(22) |
22
(23) |
23
(23) |
24
(23) |
25
(20) |
26
(19) |
|
27
(33) |
28
(20) |
29
(15) |
30
(21) |
31
(20) |
|
|
|
From: Dave G. <go...@mc...> - 2012-05-15 21:32:33
|
Was my explanation sufficiently clear/compelling to get this patch included? Is there something I can do to make this easier? Maybe a reproducer build script that clearly shows the problem? There's already plenty of user pain when using most HPC software. It would be great if we could remove this pain point when building Valgrind in the presence of MPI implementations. (I'm not trying to be annoying about this, but the patch is fairly small, very helpful, and it's been sitting in the bug tracker for about a year now… Feel free to tell me to buzz off if I'm becoming obnoxious.) -Dave On May 11, 2012, at 5:42 PM CDT, Dave Goodell wrote: > On May 11, 2012, at 5:25 PM CDT, Philippe Waroquiers wrote: > >> On Fri, 2012-05-11 at 09:56 +0200, Julian Seward wrote: >>> (kind-of unrelated) >>> There's also a configure script change from Dave w.r.t. MPI, >>> that we should take, #274078 I think. >> >> I took a quick look at this but I am not too sure I understand the >> problem (and I have no mpi installation to experiment with). >> IIUC, it seems linked with static mpi library. > > The issue is that the configure logic that checks for a functional "mpicc" script doesn't match up with the actual build logic used at "make" time. So it's possible to end up with Valgrind "successfully" detecting an mpicc that can't actually build the MPI wrappers. > > One very common scenario is where MPICH2 is built with static libs only (the default) but the MPI wrappers are built relocatable: > > http://thread.gmane.org/gmane.comp.debugging.valgrind/11102/focus=11105 > > Another scenario is on Darwin when the MPI library has only been built for one architecture but Valgrind is building bi-arch, so one of the architectures fails: > > http://thread.gmane.org/gmane.comp.debugging.valgrind/12039/focus=12041 > >> Note that with the introduction of --soname-synonyms in rev 12559, >> it should be possible to support a statically linked mpi library >> with small modifications in the mpi wrappers. > > This would probably help reduce the number of failures due to the first scenario, but the improved configure logic should still be implemented. The MPI implementation may not be compatible with building the Valgrind MPI wrappers for a variety of reasons, and Valgrind users shouldn't get bizarre make-time failures when building Valgrind. |
|
From: <sv...@va...> - 2012-05-15 21:16:35
|
philippe 2012-05-15 22:16:28 +0100 (Tue, 15 May 2012)
New Revision: 12565
Log:
NEWS entry for revision 12564 (bypass gcc 4.4/gcc 4.5 bug)
Modified files:
trunk/NEWS
Modified: trunk/NEWS (+1 -0)
===================================================================
--- trunk/NEWS 2012-05-15 22:04:31 +01:00 (rev 12564)
+++ trunk/NEWS 2012-05-15 22:16:28 +01:00 (rev 12565)
@@ -101,6 +101,7 @@
298394 s390x: Don't bail out on an unknown machine model. Assume it's a new model.
298943 massif asserts with --pages-as-heap=yes when brk is changing by value different of page size
299756 for symmetry, --free-fill must be ignored for MEMPOOL_FREE and FREELIKE client requests
+n-i-bz bypass gcc4.4/4.5 wrong code generation causing out of memory or asserts
Release 3.7.0 (5 November 2011)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
From: <sv...@va...> - 2012-05-15 21:04:40
|
philippe 2012-05-15 22:04:31 +0100 (Tue, 15 May 2012)
New Revision: 12564
Log:
Bypass gcc 4.4/4.5 compilation bug by moving -fomit-frame-pointer to Makefile.all.am
gcc 4.4 and 4.5 has a bug which causes miscompilation of mc_main.c:
args are not correctly given to VG_(am_munmap_valgrind).
This causes the secondary map entries to not be unmapped
(which can cause unlimited memory growth)
and/or causes the assert on VG_(am_munmap_valgrind) result to fail.
Removing the pragma optimize from mc_main.c and inserting it instead
in Makefile.all.am for x86 solves the gcc bug.
Modified files:
trunk/Makefile.all.am
trunk/memcheck/mc_main.c
Modified: trunk/memcheck/mc_main.c (+0 -9)
===================================================================
--- trunk/memcheck/mc_main.c 2012-05-13 23:58:09 +01:00 (rev 12563)
+++ trunk/memcheck/mc_main.c 2012-05-15 22:04:31 +01:00 (rev 12564)
@@ -50,15 +50,6 @@
#include "memcheck.h" /* for client requests */
-/* We really want this frame-pointer-less on all platforms, since the
- helper functions are small and called very frequently. By default
- on x86-linux, though, Makefile.all.am doesn't specify it, so do it
- here. Requires gcc >= 4.4, unfortunately. */
-#if __GNUC__ > 4 || (__GNUC__ == 4 && __GNUC_MINOR__ >= 4)
-# pragma GCC optimize("-fomit-frame-pointer")
-#endif
-
-
/* Set to 1 to do a little more sanity checking */
#define VG_DEBUG_MEMORY 0
Modified: trunk/Makefile.all.am (+4 -4)
===================================================================
--- trunk/Makefile.all.am 2012-05-13 23:58:09 +01:00 (rev 12563)
+++ trunk/Makefile.all.am 2012-05-15 22:04:31 +01:00 (rev 12564)
@@ -133,13 +133,13 @@
endif
AM_FLAG_M3264_X86_LINUX = @FLAG_M32@
-AM_CFLAGS_X86_LINUX = @FLAG_M32@ @PREFERRED_STACK_BOUNDARY@ \
- $(AM_CFLAGS_BASE)
+AM_CFLAGS_X86_LINUX = @FLAG_M32@ @PREFERRED_STACK_BOUNDARY@ \
+ $(AM_CFLAGS_BASE) -fomit-frame-pointer
AM_CCASFLAGS_X86_LINUX = @FLAG_M32@ -g
AM_FLAG_M3264_AMD64_LINUX = @FLAG_M64@
-AM_CFLAGS_AMD64_LINUX = @FLAG_M64@ -fomit-frame-pointer \
- @PREFERRED_STACK_BOUNDARY@ $(AM_CFLAGS_BASE)
+AM_CFLAGS_AMD64_LINUX = @FLAG_M64@ @PREFERRED_STACK_BOUNDARY@ \
+ $(AM_CFLAGS_BASE) -fomit-frame-pointer
AM_CCASFLAGS_AMD64_LINUX = @FLAG_M64@ -g
AM_FLAG_M3264_PPC32_LINUX = @FLAG_M32@
|
|
From: 王 <wan...@cn...> - 2012-05-15 11:42:22
|
Hello everyone. Massif is a heap and stack profiler, I have a question about massif when I use it. It is that I can’t get the output log(massif.out.pid) until the program tested is over. If the program tested is just like endless while sentence, how can I get the massif log. Thank you. ************************************************ WangYang PSDCD DSDC Room401,15#,NO.23 Soft Park East Road ,Dalian,116023,P,R.China Tel:+86-411-8476-8550-6069 E-mail: wan...@cn... ************************************************ |
|
From: Julian S. <js...@ac...> - 2012-05-15 08:09:47
|
> code since it need to build an "env" first. Any potential solution to > this? Thanks! There is no zero-effort solution :-( Probably the simplest and most general thing to do is to enhance the amd64 doHelperCall() function so that it can generate code to pass arguments on the stack as well as in registers. The limit of 6 is because the ELF x86_64 ABI passes the first 6 args in registers and the rest on the stack. You will need to look at the ELF x86_64 ABI document, which I think you can get from http://www.x86-64.org/documentation/abi.pdf J |