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
(7) |
|
2
(8) |
3
(8) |
4
(7) |
5
(9) |
6
(9) |
7
(7) |
8
(7) |
|
9
(7) |
10
(6) |
11
(6) |
12
(8) |
13
(10) |
14
(14) |
15
(7) |
|
16
(7) |
17
(8) |
18
(7) |
19
(6) |
20
(8) |
21
(7) |
22
(7) |
|
23
(7) |
24
(12) |
25
(7) |
26
(7) |
27
(16) |
28
(12) |
29
(7) |
|
30
(10) |
31
(8) |
|
|
|
|
|
|
From: <sv...@va...> - 2006-07-27 23:48:56
|
Author: sewardj
Date: 2006-07-28 00:48:53 +0100 (Fri, 28 Jul 2006)
New Revision: 5991
Log:
Leak checking fixes from Graydon Hoare:
- fix off by one error in binary searches
- extend leak checking functionality to memory pools
Modified:
trunk/memcheck/mc_leakcheck.c
Modified: trunk/memcheck/mc_leakcheck.c
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- trunk/memcheck/mc_leakcheck.c 2006-07-27 23:12:17 UTC (rev 5990)
+++ trunk/memcheck/mc_leakcheck.c 2006-07-27 23:48:53 UTC (rev 5991)
@@ -175,7 +175,7 @@
PROF_EVENT(71, "find_shadow_for_OLD(loop)");
a_lo =3D shadows[i]->data;
a_hi =3D ((Addr)shadows[i]->data) + shadows[i]->size;
- if (a_lo <=3D ptr && ptr <=3D a_hi)
+ if (a_lo <=3D ptr && ptr < a_hi)
return i;
}
return -1;
@@ -206,11 +206,11 @@
hi =3D mid-1;
continue;
}=20
- if (ptr > a_mid_hi) {
+ if (ptr >=3D a_mid_hi) {
lo =3D mid+1;
continue;
}
- tl_assert(ptr >=3D a_mid_lo && ptr <=3D a_mid_hi);
+ tl_assert(ptr >=3D a_mid_lo && ptr < a_mid_hi);
retVal =3D mid;
break;
}
@@ -345,7 +345,8 @@
return;
=20
tl_assert(sh_no >=3D 0 && sh_no < lc_n_shadows);
- tl_assert(ptr <=3D lc_shadows[sh_no]->data + lc_shadows[sh_no]->size)=
;
+ tl_assert(ptr >=3D lc_shadows[sh_no]->data);
+ tl_assert(ptr < lc_shadows[sh_no]->data + lc_shadows[sh_no]->size);
=20
if (lc_markstack[sh_no].state =3D=3D Unreached) {
if (0)
@@ -673,6 +674,107 @@
}
}
=20
+static MC_Chunk**
+find_active_shadows(UInt* n_shadows)
+{
+ /* Our goal is to construct a set of shadows that includes every
+ * mempool chunk, and every malloc region that *doesn't* contain a
+ * mempool chunk. We do this in several phases.
+ *
+ * First we collect all the malloc chunks into an array and sort it.
+ * We do this because we want to query the chunks by interior
+ * pointers, requiring binary search.
+ *
+ * Second we build an array containing a Bool for each malloc chunk,
+ * indicating whether it contains any mempools.
+ *
+ * Third we loop over the mempool tables. For each chunk in each
+ * pool, we set the entry in the Bool array corresponding to the
+ * malloc chunk containing the mempool chunk.
+ *
+ * Finally we copy the mempool chunks and the non-marked malloc
+ * chunks into a combined array of shadows, free our temporaries,
+ * and return the combined array.
+ */
+
+ MC_Mempool *mp;
+ MC_Chunk **mallocs, **shadows, *mc;
+ UInt n_mallocs, m, s;
+ Bool *malloc_chunk_holds_a_pool_chunk;
+
+ mallocs =3D (MC_Chunk**) VG_(HT_to_array)( MC_(malloc_list), &n_mallo=
cs );
+
+ if (n_mallocs =3D=3D 0) {
+ tl_assert(mallocs =3D=3D NULL);
+ *n_shadows =3D 0;
+ return NULL;
+ }
+
+ VG_(ssort)((void*)mallocs, n_mallocs,=20
+ sizeof(VgHashNode*), lc_compar);
+
+ malloc_chunk_holds_a_pool_chunk =3D VG_(calloc)( n_mallocs, sizeof(Bo=
ol) );
+
+ *n_shadows =3D n_mallocs;
+
+ VG_(HT_ResetIter)(MC_(mempool_list));
+ while ( (mp =3D VG_(HT_Next)(MC_(mempool_list))) ) {
+ VG_(HT_ResetIter)(mp->chunks);
+ while ( (mc =3D VG_(HT_Next)(mp->chunks)) ) {
+
+ /* We'll need a shadow for this chunk. */
+ ++(*n_shadows);
+
+ /* Possibly invalidate the malloc holding the beginning of this=
chunk. */
+ m =3D find_shadow_for(mc->data, mallocs, n_mallocs);
+ if (m !=3D -1 && malloc_chunk_holds_a_pool_chunk[m] =3D=3D Fals=
e) {
+ tl_assert(*n_shadows > 0);
+ --(*n_shadows);
+ malloc_chunk_holds_a_pool_chunk[m] =3D True;
+ }
+
+ /* Possibly invalidate the malloc holding the end of this chunk=
. */
+ if (mc->size > 1) {
+ m =3D find_shadow_for(mc->data + (mc->size - 1), mallocs, n_=
mallocs);
+ if (m !=3D -1 && malloc_chunk_holds_a_pool_chunk[m] =3D=3D F=
alse) {
+ tl_assert(*n_shadows > 0);
+ --(*n_shadows);
+ malloc_chunk_holds_a_pool_chunk[m] =3D True;
+ }
+ }
+ }
+ }
+
+ tl_assert(*n_shadows > 0);
+ shadows =3D VG_(malloc)(sizeof(VgHashNode*) * (*n_shadows));
+ s =3D 0;
+
+ /* Copy the mempool chunks into the final array. */
+ VG_(HT_ResetIter)(MC_(mempool_list));
+ while ( (mp =3D VG_(HT_Next)(MC_(mempool_list))) ) {
+ VG_(HT_ResetIter)(mp->chunks);
+ while ( (mc =3D VG_(HT_Next)(mp->chunks)) ) {
+ tl_assert(s < *n_shadows);
+ shadows[s++] =3D mc;
+ }
+ }
+
+ /* Copy the malloc chunks into the final array. */
+ for (m =3D 0; m < n_mallocs; ++m) {
+ if (!malloc_chunk_holds_a_pool_chunk[m]) {
+ tl_assert(s < *n_shadows);
+ shadows[s++] =3D mallocs[m];
+ }
+ }
+
+ tl_assert(s =3D=3D *n_shadows);
+ VG_(free)(mallocs);
+ VG_(free)(malloc_chunk_holds_a_pool_chunk);
+
+ return shadows;
+}
+
+
/* Top level entry point to leak detector. Call here, passing in
suitable address-validating functions (see comment at top of
scan_all_valid_memory above). These functions used to encapsulate th=
e
@@ -689,9 +791,7 @@
=20
tl_assert(mode !=3D LC_Off);
=20
- /* VG_(HT_to_array) allocates storage for shadows */
- lc_shadows =3D (MC_Chunk**)VG_(HT_to_array)( MC_(malloc_list),
- &lc_n_shadows );
+ lc_shadows =3D find_active_shadows(&lc_n_shadows);
=20
/* Sort the array. */
VG_(ssort)((void*)lc_shadows, lc_n_shadows, sizeof(VgHashNode*), lc_c=
ompar);
|
|
From: <sv...@va...> - 2006-07-27 23:15:29
|
Author: njn Date: 2006-07-28 00:15:23 +0100 (Fri, 28 Jul 2006) New Revision: 289 Log: Add Squid. Modified: trunk/gallery/users.html Modified: trunk/gallery/users.html =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/gallery/users.html 2006-07-27 23:07:11 UTC (rev 288) +++ trunk/gallery/users.html 2006-07-27 23:15:23 UTC (rev 289) @@ -692,6 +692,9 @@ =20 <ul> =20 + <li><a href=3D"http://www.squid-cache.org/">Squid:</a> + A full-featured web proxy cache.</li> + <li><a href=3D"http://www.powerdns.com/">PowerDNS:</a> a modern, advanced and high performance authoritative-only nameserver.</li> |
|
From: Bryan M. <om...@br...> - 2006-07-27 23:15:22
|
Nick, nearly forgot (been a little busy of late) Would you mind adding something along the lines of: Omega - an instant memory leak detector tool designed to give the location that a leak occurs, as it occurs. http://www.brainmurders.eclipse.co.uk/omega.html Cheers, Bryan "Brain Murders" Meredith Nicholas Nethercote wrote: > On Thu, 13 Jul 2006, Bryan Meredith wrote: > >> What would be a good way to approach the project team as "your stuff >> leaks here - my experimental tool says so (and so does this one)" is >> probably not going to make me any friends... > > I don't think there's harm in telling people. It's just a bug report, > people should be happy to get them, especially if it has good info on what > the root cause is. You could say "your program has a leak here, and by the > way I used my tool Omega to automatically find it". > >> Finally, how do I go about requesting a link to Omega be added to your >> patches page and what criteria would I have to meet? > > There's no real criteria... I'm happy to add something to the > Variants/Patches page. Can you give me a one sentence description and a > URL to link to? > > Nick > > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Valgrind-developers mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-developers > |
|
From: <sv...@va...> - 2006-07-27 23:12:22
|
Author: sewardj
Date: 2006-07-28 00:12:17 +0100 (Fri, 28 Jul 2006)
New Revision: 5990
Log:
When doing leak checks, don't poke around in device segments as this
may hang the entire machine. (Tom Hughes).
Modified:
trunk/memcheck/mc_leakcheck.c
Modified: trunk/memcheck/mc_leakcheck.c
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- trunk/memcheck/mc_leakcheck.c 2006-07-24 10:14:37 UTC (rev 5989)
+++ trunk/memcheck/mc_leakcheck.c 2006-07-27 23:12:17 UTC (rev 5990)
@@ -763,6 +763,21 @@
continue;
if (seg->isCH)
continue;
+
+ /* Don't poke around in device segments as this may cause
+ hangs. Exclude /dev/zero just in case someone allocated
+ memory by explicitly mapping /dev/zero. */
+ if (seg->kind =3D=3D SkFileC=20
+ && (VKI_S_ISCHR(seg->mode) || VKI_S_ISBLK(seg->mode))) {
+ HChar* dev_name =3D VG_(am_get_filename)( seg );
+ if (dev_name && 0 =3D=3D VG_(strcmp)(dev_name, "/dev/zero")) =
{
+ /* don't skip /dev/zero */
+ } else {
+ /* skip this device mapping */
+ continue;
+ }
+ }
+
if (0)
VG_(printf)("ACCEPT %2d %p %p\n", i, seg->start, seg->end);
lc_scan_memory(seg->start, seg->end+1 - seg->start);
|
|
From: <sv...@va...> - 2006-07-27 23:07:15
|
Author: njn Date: 2006-07-28 00:07:11 +0100 (Fri, 28 Jul 2006) New Revision: 288 Log: wibbles Modified: trunk/downloads/old.html Modified: trunk/downloads/old.html =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/downloads/old.html 2006-07-27 23:05:10 UTC (rev 287) +++ trunk/downloads/old.html 2006-07-27 23:07:11 UTC (rev 288) @@ -62,16 +62,13 @@ 2.6 and glibc 2.2.X or 2.3.X.</p> =20 =20 - +<div class=3D"hr_brown"><hr/></div> <h3>Valgrind for PowerPC</h3> =20 <p>Paul Mackerras' PPC32/Linux port of Valgrind 2.4.1 is now available h= ere: <a href=3D"/downloads/pmk/valgrind-2.4.1-ppc.tar.bz2"> valgrind-2.4.1-ppc (tar.bz2)</a> [1078kB]. Thanks to Craig Chaney of -IBM for testing, bug-finding and for the core dump code. If you use -it and find it useful, I would love to hear about it (email paulus at -valgrind.org). If you find bugs or deficiencies in it, I'd like -to hear about that too. +IBM for testing, bug-finding and for the core dump code. =20 </p> =20 <p>There are three older versions of the PowerPC/Linux port available, |
|
From: <sv...@va...> - 2006-07-27 23:05:16
|
Author: njn Date: 2006-07-28 00:05:10 +0100 (Fri, 28 Jul 2006) New Revision: 287 Log: Moved Paul Mac's old PPC32 stuff to the release archive from the Variants/Patches page, because it's now of historical interest only. Removed: trunk/downloads/pmk/pmk.html Modified: trunk/downloads/old.html trunk/downloads/variants.html Modified: trunk/downloads/old.html =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/downloads/old.html 2006-07-14 06:02:17 UTC (rev 286) +++ trunk/downloads/old.html 2006-07-27 23:05:10 UTC (rev 287) @@ -63,6 +63,31 @@ =20 =20 =20 +<h3>Valgrind for PowerPC</h3> + +<p>Paul Mackerras' PPC32/Linux port of Valgrind 2.4.1 is now available h= ere: +<a href=3D"/downloads/pmk/valgrind-2.4.1-ppc.tar.bz2"> +valgrind-2.4.1-ppc (tar.bz2)</a> [1078kB]. Thanks to Craig Chaney of +IBM for testing, bug-finding and for the core dump code. If you use +it and find it useful, I would love to hear about it (email paulus at +valgrind.org). If you find bugs or deficiencies in it, I'd like +to hear about that too. +</p> + +<p>There are three older versions of the PowerPC/Linux port available, +mainly of historical interest: a PPC/Linux version of the Valgrind +2.2.0 release: +<a href=3D"/downloads/pmk/valgrind-2.2.0-ppc.tar.bz2">valgrind-2.2.0-ppc +(tar.bz2)</a> [984kB], a version based on the Valgrind development +version from CVS as of 17 December 2004: +<a href=3D"/downloads/pmk/valgrind-2.3.0.CVS-ppc-041217.tar.bz2"> +valgrind-2.3.0.CVS-ppc-041217 (tar.bz2)</a> [920kB], +and a PPC/Linux version of the Valgrind 2.4.0 release: +<a href=3D"/downloads/pmk/valgrind-2.4.0-ppc.tar.bz2"> +valgrind-2.4.0-ppc (tar.bz2)</a> [1093kB].</p> +<p> + + <div class=3D"hr_brown"><hr/></div> <h3>valgrind-2.4.1</h3> =20 Deleted: trunk/downloads/pmk/pmk.html =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/downloads/pmk/pmk.html 2006-07-14 06:02:17 UTC (rev 286) +++ trunk/downloads/pmk/pmk.html 2006-07-27 23:05:10 UTC (rev 287) @@ -1,22 +0,0 @@ -<h3>Paul Mackerras' Stuff</h3> - -<p>The PowerPC/Linux port of Valgrind 2.4.1 is now available here: -<a href=3D"/downloads/pmk/valgrind-2.4.1-ppc.tar.bz2"> -valgrind-2.4.1-ppc (tar.bz2)</a> [1078kB]. Thanks to Craig Chaney of -IBM for testing, bug-finding and for the core dump code. If you use -it and find it useful, I would love to hear about it (email paulus at -valgrind.org). If you find bugs or deficiencies in it, I'd like -to hear about that too. -</p> - -<p>There are three older versions of the PowerPC/Linux port available, -mainly of historical interest: a PPC/Linux version of the Valgrind -2.2.0 release: -<a href=3D"/downloads/pmk/valgrind-2.2.0-ppc.tar.bz2">valgrind-2.2.0-ppc -(tar.bz2)</a> [984kB], a version based on the Valgrind development -version from CVS as of 17 December 2004: -<a href=3D"/downloads/pmk/valgrind-2.3.0.CVS-ppc-041217.tar.bz2"> -valgrind-2.3.0.CVS-ppc-041217 (tar.bz2)</a> [920kB], -and a PPC/Linux version of the Valgrind 2.4.0 release: -<a href=3D"/downloads/pmk/valgrind-2.4.0-ppc.tar.bz2"> -valgrind-2.4.0-ppc (tar.bz2)</a> [1093kB].</p> Modified: trunk/downloads/variants.html =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/downloads/variants.html 2006-07-14 06:02:17 UTC (rev 286) +++ trunk/downloads/variants.html 2006-07-27 23:05:10 UTC (rev 287) @@ -33,11 +33,6 @@ include './jsf/jsf.html'; break; =20 - case 'pmk': - echo '<a href=3D"/downloads/variants.html">Back</a><br />'."\n"; - include './pmk/pmk.html'; - break; - default: ?> <br /> @@ -60,11 +55,6 @@ other adds support for pool-based allocators.</p> =20 =20 -<p><b>Paul Mackerras</b> has=20 -<a href=3D"/downloads/variants.html?pmk">ported Valgrind to run on -32-bit PowerPC Linux</a> machines.</p> - - <p><b>Adam Gundy</b> <arg at cyberscience com> supplied a variant of the 20031012 stable release that is capable of running Wine on Valgrind. A big thanks to him.</p> |
|
From: Julian S. <js...@ac...> - 2006-07-27 21:11:06
|
I believe that shipped together with V 3.1.0 and 3.1.1. Then it was then merged into the main source tree and so 3.2.0 has callgrind 'built in', so to speak. There are a few regression tests for it, but more would be no bad thing. J On Thursday 27 July 2006 00:09, Dave Nomura wrote: > Can anyone tell me where this RPM: valgrind-callgrind-0.10.1-2.EL4 > might have come from (what source tree version). > > I am trying to figure out a strategy for testing this tool and was > hoping to find some regression tests for it. If this was built from a > source tree newer than 3.1.1 then maybe I should try running the > callgrind/tests regression tests from the current SVN sources. > > Any suggestions? > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your opinions on IT & business topics through brief surveys -- and earn > cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Valgrind-developers mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-developers |
|
From: Tom H. <to...@co...> - 2006-07-27 14:53:36
|
In message <44C...@us...>
Dave Nomura <dc...@us...> wrote:
> Can anyone tell me where this RPM: valgrind-callgrind-0.10.1-2.EL4
> might have come from (what source tree version).
Looks like a RedHat Enterprise Linux 4 package to me
Certainly valgrind-callgrind is the name RedHat used for the callgrind
package in Fedora and I assume Enterprise is the same, and the EL4 at
the end of the release usually indicates an Enterprise Linux 4 package.
Doubtless "rpm -qi" would confirm it...
> I am trying to figure out a strategy for testing this tool and was
> hoping to find some regression tests for it. If this was built from a
> source tree newer than 3.1.1 then maybe I should try running the
> callgrind/tests regression tests from the current SVN sources.
Well it's come from the callgrind 0.10.1 source tree - it predates
the point at which callgrind was included in the main valgrind source
tree.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|
|
From: Tom H. <th...@cy...> - 2006-07-27 14:44:07
|
Nightly build on alvis ( i686, Red Hat 7.3 ) started at 2006-07-27 03:15:02 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 == 236 tests, 19 stderr failures, 0 stdout failures, 0 posttest failures == memcheck/tests/addressable (stderr) memcheck/tests/badjump (stderr) memcheck/tests/describe-block (stderr) memcheck/tests/erringfds (stderr) memcheck/tests/leak-0 (stderr) memcheck/tests/leak-cycle (stderr) memcheck/tests/leak-regroot (stderr) memcheck/tests/leak-tree (stderr) memcheck/tests/match-overrun (stderr) memcheck/tests/mempool (stderr) memcheck/tests/partial_load_dflt (stderr) memcheck/tests/partial_load_ok (stderr) memcheck/tests/partiallydefinedeq (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/sigkill (stderr) memcheck/tests/stack_changes (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/scalar_supp (stderr) memcheck/tests/xml1 (stderr) |
|
From: Tom H. <th...@cy...> - 2006-07-27 14:33:28
|
Nightly build on gill ( x86_64, Fedora Core 2 ) started at 2006-07-27 03:00:07 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 == 260 tests, 4 stderr failures, 0 stdout failures, 0 posttest failures == memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/scalar_supp (stderr) none/tests/fdleak_fcntl (stderr) |
|
From: <js...@ac...> - 2006-07-27 12:11:18
|
Nightly build on phoenix ( SuSE 10.0 ) started at 2006-07-27 03:30:01 BST 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 == 235 tests, 4 stderr failures, 0 stdout failures, 0 posttest failures == memcheck/tests/leak-tree (stderr) memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/scalar_supp (stderr) |
|
From: <js...@ac...> - 2006-07-27 11:49:05
|
Nightly build on minnie ( SuSE 10.0, ppc32 ) started at 2006-07-27 09:00:01 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 == 206 tests, 11 stderr failures, 5 stdout failures, 0 posttest failures == memcheck/tests/leak-cycle (stderr) memcheck/tests/leak-tree (stderr) memcheck/tests/leakotron (stdout) memcheck/tests/mempool (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/sigaltstack (stderr) memcheck/tests/xml1 (stderr) none/tests/faultstatus (stderr) none/tests/mremap (stderr) 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: Nicholas N. <nj...@cs...> - 2006-07-27 11:07:36
|
On Wed, 26 Jul 2006, Dave Nomura wrote: > Does anyone have any ideas on how to find out what the results of > running the regression test suite against the 3.1.1 release for PPC > should look like? I am using a machine with valgrind-3.1.1-1.EL4 RPM > installed. > > I'm seeing: > == 175 tests, 13 stderr failures, 1 stdout failure ================= > memcheck/tests/leak-cycle (stderr) > memcheck/tests/leak-tree (stderr) > memcheck/tests/partiallydefinedeq (stderr) > memcheck/tests/pointer-trace (stderr) > memcheck/tests/supp1 (stderr) > memcheck/tests/supp_unknown (stderr) > memcheck/tests/toobig-allocs (stderr) > memcheck/tests/xml1 (stderr) > massif/tests/toobig-allocs (stderr) > none/tests/faultstatus (stderr) > none/tests/fdleak_cmsg (stderr) > none/tests/fdleak_socketpair (stderr) > none/tests/mremap (stderr) > none/tests/mremap2 (stdout) > > but have no idea whether any of these tests should have passed. Are > there archived expected regression suite results archived somewhere? No. Unfortunately it's quite variable, and very difficult to get them all passing. Generally, when making a change it's a case of "has the set of failing regression tests changed" rather than "are any regression tests failing". The ones failing above all look familiar. One thing you can do is look at the *.stderr.diff and *.stdout.diff files. In a lot of cases, you'll see it's just a small variation from what's expected Hopefully that will be reassuring! Nick |
|
From: Dave N. <dc...@us...> - 2006-07-27 10:40:22
|
Does anyone have any ideas on how to find out what the results of running the regression test suite against the 3.1.1 release for PPC should look like? I am using a machine with valgrind-3.1.1-1.EL4 RPM installed. I'm seeing: == 175 tests, 13 stderr failures, 1 stdout failure ================= memcheck/tests/leak-cycle (stderr) memcheck/tests/leak-tree (stderr) memcheck/tests/partiallydefinedeq (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/supp1 (stderr) memcheck/tests/supp_unknown (stderr) memcheck/tests/toobig-allocs (stderr) memcheck/tests/xml1 (stderr) massif/tests/toobig-allocs (stderr) none/tests/faultstatus (stderr) none/tests/fdleak_cmsg (stderr) none/tests/fdleak_socketpair (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) but have no idea whether any of these tests should have passed. Are there archived expected regression suite results archived somewhere? I am running on a PPC970FX w/ altivec running Red Hat Enterprise Linux AS release 4 (Nahant Update 4 Beta) |
|
From: Tom H. <th...@cy...> - 2006-07-27 05:35:47
|
Nightly build on ford ( i686, Fedora Core 4 ) started at 2006-07-27 03:25: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 == 235 tests, 5 stderr failures, 0 stdout failures, 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) |
|
From: Tom H. <to...@co...> - 2006-07-27 04:18:09
|
Nightly build on dunsmere ( athlon, Fedora Core 5 ) started at 2006-07-27 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, 5 stderr failures, 0 stdout failures, 0 posttest failures == memcheck/tests/mempool (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/xml1 (stderr) |