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
(13) |
3
(7) |
|
4
(9) |
5
(23) |
6
(19) |
7
(18) |
8
(2) |
9
(7) |
10
(21) |
|
11
(13) |
12
|
13
(8) |
14
(17) |
15
(19) |
16
(25) |
17
(43) |
|
18
(22) |
19
(12) |
20
(19) |
21
(12) |
22
(9) |
23
(12) |
24
(5) |
|
25
(16) |
26
(25) |
27
(24) |
28
(19) |
29
(26) |
30
(25) |
31
(6) |
|
From: Julian S. <js...@ac...> - 2004-07-18 12:31:10
|
> 2.1.2 works for me. Good! > The new_override regtest failed, because the .stdout.exp file was missing, > which I've now fixed in CVS; it's not a big problem. (And > pth_cancel2 usually fails, but that's normal for me...) Tarball downloading folks won't be doing make regtest, I guess, so that's not a big deal. > Thanks to Julian for doing the release! And to Tom for a swathe of recent > bug fixes. Well, in fact, thanks to all who contributed. I think it's become a much more stable and mature system in the last year, what with the new syscall stuff and FV changes, and I'm particularly pleased with the fact that we are able to track new distros, and specifically NPTL, which had me worried for a long time. J |
|
From: Nicholas N. <nj...@ca...> - 2004-07-18 12:09:20
|
Hi, 2.1.2 works for me. The new_override regtest failed, because the .stdout.exp file was missing, which I've now fixed in CVS; it's not a big problem. (And pth_cancel2 usually fails, but that's normal for me...) Thanks to Julian for doing the release! And to Tom for a swathe of recent bug fixes. N |
|
From: Nicholas N. <nj...@ca...> - 2004-07-18 12:05:46
|
CVS commit by nethercote:
Include new_override.stdout.exp in 'make dist'.
M +1 -1 Makefile.am 1.38
--- valgrind/memcheck/tests/Makefile.am #1.37:1.38
@@ -50,5 +50,5 @@
nanoleak_supp.stderr.exp nanoleak_supp.vgtest nanoleak.supp \
new_nothrow.stderr.exp new_nothrow.vgtest \
- new_override.stderr.exp new_override.vgtest \
+ new_override.stderr.exp new_override.stdout.exp new_override.vgtest \
null_socket.stderr.exp null_socket.vgtest \
overlap.stderr.exp overlap.stdout.exp overlap.vgtest \
|
|
From: Julian S. <js...@ac...> - 2004-07-18 11:49:36
|
Freeze over. I tagged the tree at VALGRIND_2_1_2, as usual. The current cvs head should now report itself as 2.1.3.CVS. J |
|
From: Julian S. <js...@ac...> - 2004-07-18 11:48:01
|
CVS commit by jseward: --> 2.1.3.CVS M +1 -1 configure.in 1.114 --- valgrind/configure.in #1.113:1.114 @@ -2,5 +2,5 @@ AC_INIT(coregrind/vg_main.c) # give me a source file, any source file... AM_CONFIG_HEADER(config.h) -AM_INIT_AUTOMAKE(valgrind, 2.1.2) +AM_INIT_AUTOMAKE(valgrind, 2.1.3.CVS) AM_MAINTAINER_MODE |
|
From: Julian S. <js...@ac...> - 2004-07-18 11:34:44
|
CVS commit by jseward: Update the MD5 for 2.1.2. M +2 -2 downloads.html 1.14 --- devel-home/valgrind/downloads.html #1.13:1.14 @@ -29,6 +29,6 @@ <strong>2.1.2 (of 18 July 2004)</strong> - <a HREF="http://developer.kde.org/~sewardj/valgrind-2.1.2.tar.bz2">(bzip2'd source, 961KB)</a> - (MD5=646d42f7e2be4745842e2ff76b62fbc0) + <a HREF="http://developer.kde.org/~sewardj/valgrind-2.1.2.tar.bz2">(bzip2'd source, 962KB)</a> + (MD5=585e3ac5f7b86d6cd3e2bed07af732de) <p> 2.1.2 contains four months worth of bug fixes and refinements. |
|
From: Nicholas N. <nj...@ca...> - 2004-07-18 11:30:35
|
CVS commit by nethercote: Removed some older news items from the front page (still viewable in the news.html page). M +0 -6 index.html 1.23 --- devel-home/valgrind/index.html #1.22:1.23 @@ -11,10 +11,4 @@ <p class="news">March 04, 2004: An experimental PowerPC port is available. See <a href="related.html">Related Projects</a>. - -<p class="news">February 15, 2004: Valgrind CVS now includes Massif, a heap -profiling tool. - -<p class="news">January 27, 2004: We have a new page listing -<a href="users.html">projects using Valgrind</a>. <hr> |
|
From: Julian S. <js...@ac...> - 2004-07-18 11:07:59
|
CVS commit by jseward:
This was getting a bit old.
M +11 -12 sysreqs.html 1.7
--- devel-home/valgrind/sysreqs.html #1.6:1.7
@@ -14,26 +14,25 @@
<h3>Operating System</h3>
You must be running Linux kernel 2.4.X, 2.5.X or 2.6.X, and glibc 2.2.X or
-2.3.X. That covers the vast majority of installed systems at present. Ancient
-systems (glibc-2.1.3, Red Hat 6.2 for example) might still work with some
-effort (they once used to), but don't bet on it.
+2.3.X. That covers the vast majority of installed systems at present.
+The oldest system we test on is Red Hat 7.2, which is getting pretty
+long in the tooth by now.
<p>
-The 2.0.0 stable release is known to build and run on Red Hats 7.3,
-8, 9, SuSE 8.0 and SuSE 8.2. Chances are good that it will build and
+The 2.1.2 stable release is known to build and run on Red Hats 7.2,
+7.3, 8, 9, Fedora Core 2 and SuSE 9.1. It should work on both NPTL and
+PosixThreads based systems. Chances are good that it will build and
work for you if you have any non-ancient Linux distribution.
<p>
+The 2.0.0 stable release is known to build and run on Red Hats 7.3,
+8, 9, SuSE 8.0 and SuSE 8.2.
+<p>
<h3>Limitations</h3>
-There are some, the most significant of which are:
+There are some, the most significant of which is:
<ul>
-<li>Incomplete support for SIMD instructions. 2.0.0 has complete
- MMX support, and pretty good SSE/SSE2 support, but some instructions
- are still not handled. 3DNow! (rapidly becoming 3DThen!) is not
- supported at all.
- <p>
<li>Support for non-POSIX signal stuff is flaky. If you stick to POSIX
signals you should be ok.
<p>
</ul>
-<a href="http://developer.kde.org/~sewardj/docs-2.0.0/coregrind_core.html#limits">
+<a href="http://developer.kde.org/~sewardj/docs-2.1.2/coregrind_core.html#limits">
Section 2.12 of the manual</a> contains a complete list of limitations.
<p>
|
|
From: Julian S. <js...@ac...> - 2004-07-18 11:07:36
|
CVS commit by jseward: Promoting the idea that we can't count accurately up to five is probably not good :-) M +1 -1 tools.html 1.9 --- devel-home/valgrind/tools.html #1.8:1.9 @@ -5,5 +5,5 @@ ?> -The Valgrind distribution includes four useful debugging and profiling tools. +The Valgrind distribution includes five useful debugging and profiling tools. <ul> |
|
From: Julian S. <js...@ac...> - 2004-07-18 10:52:37
|
CVS commit by jseward: Update for Valgrind-2.1.2 release. M +4 -0 bugs.html 1.12 M +3 -3 docs.html 1.8 M +26 -49 downloads.html 1.13 M +3 -2 index.html 1.22 M +7 -2 news.html 1.6 M +2 -1 tools.html 1.8 --- devel-home/valgrind/bugs.html #1.11:1.12 @@ -32,4 +32,8 @@ <p> +Filing bug reports in bugzilla is the most effective way of getting +the developers to look at it. Mailing the developers individually +your <em>least effective</em> solution. Please use bugzilla! + <?php include "footer.inc" --- devel-home/valgrind/docs.html #1.7:1.8 @@ -5,7 +5,7 @@ ?> -<a href="http://developer.kde.org/~sewardj/docs-2.0.0/manual.html">Full -documentation</a> for version 2.0.0 is supplied, up-to-date as of 11 November -2003. +<a href="http://developer.kde.org/~sewardj/docs-2.1.2/manual.html">Full +documentation</a> for version 2.1.2 is supplied, up-to-date as of 18 +July 2004. <p> The following tutorials may be slightly out-of-date, but should give a good --- devel-home/valgrind/downloads.html #1.12:1.13 @@ -25,62 +25,39 @@ -<h3>Older Stable Releases</h3> - -None available. - <h3>Current Development Release</h3> -<strong>2.1.1 (of 12 March 2004)</strong> - <a HREF="http://developer.kde.org/~sewardj/valgrind-2.1.1.tar.bz2">(bzip2'd source, 923KB)</a> - (MD5=0010c3e8f054ecc633151c62044b646d) -<p> -2.1.1 contains some internal structural changes needed for V's -long-term future. These don't affect end-users. There are -also some useful user-visible changes. -<ul> -<li> -Greater isolation between Valgrind and the program being run, so - the program is less likely to inadvertently kill Valgrind by - doing wild writes. -<p><li> -Massif: a new space profiling tool. Try it! It's cool, and it'll - tell you in detail where and when your C/C++ code is allocating heap. - Draws pretty .ps pictures of memory use against time. A potentially - powerful tool for making sense of your program's space use. -<p><li> -Fixes for many bugs, including support for more SSE2/SSE3 instructions, - various signal/syscall things, and various problems with debug - info readers. -<p><li> -Support for glibc-2.3.3 based systems. -</ul> - -We are now doing automatic overnight build-and-test runs on a variety -of distros. As a result, we believe 2.1.1 builds and runs on: -Red Hat 7.2, 7.3, 8.0, 9, Fedora Core 1, SuSE 8.2, SuSE 9. - - +<strong>2.1.2 (of 18 July 2004)</strong> + <a HREF="http://developer.kde.org/~sewardj/valgrind-2.1.2.tar.bz2">(bzip2'd source, 961KB)</a> + (MD5=646d42f7e2be4745842e2ff76b62fbc0) +<p> +2.1.2 contains four months worth of bug fixes and refinements. +Although officially a developer release, we believe it to be stable +enough for widespread day-to-day use. 2.1.2 is pretty good, so try it +first, although there is a chance it won't work. If so then try 2.0.0 +and tell us what went wrong. 2.1.2 fixes a lot of problems present +in 2.0.0 and is generally a much better product. +<p> +Relative to 2.1.1, a large number of minor problems have +been fixed, and so if you use 2.1.1 you should try 2.1.2. Users of +the last stable release, 2.0.0, might also want to try this release. +For one thing, 2.1.2 compiles with gcc-3.4.X, whereas 2.0.0 doesn't. +<p> +The +<a HREF="http://developer.kde.org/~sewardj/docs-2.1.2/NEWS.txt">NEWS</a> +file in the distro contains a detailed list of bug fixes and changes. -<h3>Older Development Release</h3> +<p> +The 2.1.2 documentation is available on-line +<a href="http://developer.kde.org/~sewardj/docs-2.1.2/manual.html">here +</a>. -<strong>2.1.0 (of 14 December 2003)</strong> - <a HREF="http://developer.kde.org/~sewardj/valgrind-2.1.0.tar.bz2">(bzip2'd source, 762KB)</a> - (MD5=3e4056dd45163a5f555a23ced2f95191) <p> -2.1.0 brings an overhaul of syscall and signal handling, giving much -better behaviour, especially in threaded code. 2.1.0 can also check -for file descriptor leakage. A few more SSE/SSE2 instructions are -implemented, and various reported bugs have been fixed. See the <a -HREF="http://developer.kde.org/~sewardj/docs-2.1.0/NEWS.txt">NEWS</a> -file in the distro for more details. -<p> -2.1.0 is known to compile and work on: SuSE 9, SuSE 8.2, RedHat 8, -RedHat 7.3, Debian Sid. Probably works on RedHat 9, although we -haven't had explicit confirmation of that yet. - +We are now doing automatic overnight build-and-test runs on a variety +of distros. As a result, we believe 2.1.2 builds and runs on: +Red Hat 7.2, 7.3, 8.0, 9, Fedora Core 2, SuSE 9.1. --- devel-home/valgrind/index.html #1.21:1.22 @@ -5,6 +5,7 @@ ?> -<p class="news">March 12, 2004: A new unstable release, -<a href="downloads.html">valgrind 2.1.1</a>, is available. +<p class="news">July 18, 2004: A new developer release, +<a href="downloads.html">valgrind 2.1.2</a>, is available. 2.1.2 + fixes many bugs in 2.1.1, and includes the new Massif heap-profiling tool. <p class="news">March 04, 2004: An experimental PowerPC port is available. --- devel-home/valgrind/news.html #1.5:1.6 @@ -5,5 +5,10 @@ ?> -<p class="news">March 12, 2004: A new unstable release, +<p class="news">July 18, 2004: A new developer release, +<a href="downloads.html">valgrind 2.1.2</a>, is available. + 2.1.2 fixes many bugs in 2.1.1, and includes the new Massif + heap-profiling tool. + +<p class="news">March 12, 2004: A new developer release, <a href="downloads.html">valgrind 2.1.1</a>, is available. @@ -21,5 +26,5 @@ (<a href="http://builder.com.com/5100-6375-5136747.html">interview</a>). -<p class="news">December 14, 2003: A new unstable release, +<p class="news">December 14, 2003: A new developer release, <a href="downloads.html">valgrind 2.1.0</a>, is available. --- devel-home/valgrind/tools.html #1.7:1.8 @@ -65,5 +65,6 @@ allocated. Massif runs programs about 20x slower than normal. Massif was introduced in version 2.1.1 of Valgrind. - + <p> + <li><strong>Helgrind</strong> is a thread debugger which finds data races in multithreaded programs. It looks for memory locations which are |
|
From: Nicholas N. <nj...@ca...> - 2004-07-18 10:37:48
|
CVS commit by nethercote: Duplicate changes just committed to main FAQ.txt. Does anyone know how to create this faq.html by pulling in the contents of FAQ.txt from CVS? M +7 -2 faq.html 1.5 --- devel-home/valgrind/faq.html #1.4:1.5 @@ -10,5 +10,5 @@ Valgrind FAQ, version 2.1.2 ~~~~~~~~~~~~~~~~~~~~~~~~~~~ -Last revised 6 April 2004 +Last revised 18 July 2004 ~~~~~~~~~~~~~~~~~~~~~~~~~ @@ -127,7 +127,12 @@ instructions. If it still happens with newer versions, if the failing instruction is an SSE/SSE2 instruction, you might be able to recompile -your progrma without it by using the flag -march to gcc. Either way, +your program without it by using the flag -march to gcc. Either way, let us know and we'll try to fix it. +Another possibility is that your program has a bug and erroneously jumps +to a non-code address, in which case you'll get a SIGILL signal. +Memcheck/Addrcheck may issue a warning just before this happens, but they +might not if the jump happens to land in addressable memory. + ----------------------------------------------------------------- |
|
From: Nicholas N. <nj...@ca...> - 2004-07-18 10:35:47
|
CVS commit by nethercote: Extra info for FAQ. M +7 -2 FAQ.txt 1.23 --- valgrind/FAQ.txt #1.22:1.23 @@ -1,5 +1,5 @@ Valgrind FAQ, version 2.1.2 ~~~~~~~~~~~~~~~~~~~~~~~~~~~ -Last revised 6 April 2004 +Last revised 18 July 2004 ~~~~~~~~~~~~~~~~~~~~~~~~~ @@ -118,7 +118,12 @@ instructions. If it still happens with newer versions, if the failing instruction is an SSE/SSE2 instruction, you might be able to recompile -your progrma without it by using the flag -march to gcc. Either way, +your program without it by using the flag -march to gcc. Either way, let us know and we'll try to fix it. +Another possibility is that your program has a bug and erroneously jumps +to a non-code address, in which case you'll get a SIGILL signal. +Memcheck/Addrcheck may issue a warning just before this happens, but they +might not if the jump happens to land in addressable memory. + ----------------------------------------------------------------- |
|
From: Julian S. <js...@ac...> - 2004-07-18 09:25:21
|
CVS commit by jseward: --> 2.1.2 M +1 -1 configure.in 1.113 --- valgrind/configure.in #1.112:1.113 @@ -2,5 +2,5 @@ AC_INIT(coregrind/vg_main.c) # give me a source file, any source file... AM_CONFIG_HEADER(config.h) -AM_INIT_AUTOMAKE(valgrind, 2.1.2.CVS) +AM_INIT_AUTOMAKE(valgrind, 2.1.2) AM_MAINTAINER_MODE |
|
From: Julian S. <js...@ac...> - 2004-07-18 09:25:07
|
CVS commit by jseward: add #85416. M +1 -1 NEWS 1.22 --- valgrind/NEWS #1.21:1.22 @@ -61,5 +61,5 @@ 82722 Unchecked mmap in as_pad leads to mysterious failures later 78958 memcheck seg faults while running Mozilla - +85416 Arguments with colon (e.g. --logsocket) ignored |
|
From: Tom H. <th...@cy...> - 2004-07-18 08:05:50
|
CVS commit by thughes:
Only treat colons in the switch name as important when looking for a
toolname to check - colons in the switch value are now ignored.
CCMAIL: 854...@bu...
M +5 -2 vg_main.c 1.173
--- valgrind/coregrind/vg_main.c #1.172:1.173
@@ -1690,9 +1690,12 @@ static void process_cmd_line_options( UI
Char* arg = VG_(vg_argv)[i];
+ Char* colon = arg;
- // XXX: allow colons in options, for Josef
+ /* Look for a colon in the switch name */
+ while (*colon && *colon != ':' && *colon != '=')
+ colon++;
/* Look for matching "--toolname:foo" */
- if (VG_(strstr)(arg, ":")) {
+ if (*colon == ':') {
if (VG_CLO_STREQN(2, arg, "--") &&
VG_CLO_STREQN(toolname_len, arg+2, toolname) &&
|
|
From: Jarrod G. <gr...@cs...> - 2004-07-18 05:18:18
|
On Sat, 17 Jul 2004, Nicholas Nethercote wrote: > Sorry, I should have been clearer: we want to do ourselves exactly what > ld --wrap does. Ie. function replacement as we do now, but be able to > call the original function within the replacement. > > N I wonder if you could use some ideas like those in detours from M$ Research: http://research.microsoft.com/research/sn/detours/ & http://research.microsoft.com/~galenh/Publications/HuntUsenixNt99.pdf Most COTS rootkits use detours like techniques to inject code into functions. Jarrod |
|
From: <js...@ac...> - 2004-07-18 02:57:13
|
Nightly build on nemesis ( SuSE 9.1 ) started at 2004-07-18 03:50:01 BST Checking out source tree ... done Configuring ... done Building ... done Running regression tests ... done Last 20 lines of log.verbose follow memcheck/tests/overlap (stderr) memcheck/tests/pth_once (stderr) memcheck/tests/pushfpopf (stderr) memcheck/tests/realloc1 (stderr) memcheck/tests/realloc2 (stderr) memcheck/tests/realloc3 (stderr) memcheck/tests/sigaltstack (stderr) memcheck/tests/signal2 (stderr) memcheck/tests/supp1 (stderr) memcheck/tests/supp2 (stderr) memcheck/tests/suppfree (stderr) memcheck/tests/threadederrno (stderr) memcheck/tests/toobig-allocs (stderr) memcheck/tests/trivialleak (stderr) memcheck/tests/tronical (stderr) memcheck/tests/weirdioctl (stderr) memcheck/tests/writev (stderr) memcheck/tests/zeropage (stderr) make: *** [regtest] Error 1 |
|
From: Tom H. <to...@co...> - 2004-07-18 02:26:32
|
Nightly build on dunsmere ( Fedora Core 2 ) started at 2004-07-18 03:20:04 BST Checking out source tree ... done Configuring ... done Building ... done Running regression tests ... done Last 20 lines of log.verbose follow shorts: valgrind ./shorts smc1: valgrind ./smc1 susphello: valgrind ./susphello syscall-restart1: valgrind ./syscall-restart1 syscall-restart2: valgrind ./syscall-restart2 system: valgrind ./system yield: valgrind ./yield -- Finished tests in none/tests ---------------------------------------- == 173 tests, 7 stderr failures, 1 stdout failure ================= corecheck/tests/fdleak_cmsg (stderr) corecheck/tests/fdleak_fcntl (stderr) corecheck/tests/fdleak_ipv4 (stderr) corecheck/tests/fdleak_socketpair (stderr) memcheck/tests/buflen_check (stderr) memcheck/tests/execve (stderr) memcheck/tests/writev (stderr) none/tests/exec-sigmask (stdout) make: *** [regtest] Error 1 |
|
From: Tom H. <th...@cy...> - 2004-07-18 02:19:10
|
Nightly build on audi ( Red Hat 9 ) started at 2004-07-18 03:15:02 BST Checking out source tree ... done Configuring ... done Building ... done Running regression tests ... done Last 20 lines of log.verbose follow shortpush: valgrind ./shortpush shorts: valgrind ./shorts smc1: valgrind ./smc1 susphello: valgrind ./susphello syscall-restart1: valgrind ./syscall-restart1 syscall-restart2: valgrind ./syscall-restart2 system: valgrind ./system yield: valgrind ./yield -- Finished tests in none/tests ---------------------------------------- == 173 tests, 7 stderr failures, 0 stdout failures ================= corecheck/tests/fdleak_cmsg (stderr) corecheck/tests/fdleak_fcntl (stderr) corecheck/tests/fdleak_ipv4 (stderr) corecheck/tests/fdleak_socketpair (stderr) memcheck/tests/buflen_check (stderr) memcheck/tests/execve (stderr) memcheck/tests/writev (stderr) make: *** [regtest] Error 1 |
|
From: Tom H. <th...@cy...> - 2004-07-18 02:14:27
|
Nightly build on ginetta ( Red Hat 8.0 ) started at 2004-07-18 03:10:02 BST Checking out source tree ... done Configuring ... done Building ... done Running regression tests ... done Last 20 lines of log.verbose follow sem: valgrind ./sem semlimit: valgrind ./semlimit sha1_test: valgrind ./sha1_test shortpush: valgrind ./shortpush shorts: valgrind ./shorts smc1: valgrind ./smc1 susphello: valgrind ./susphello syscall-restart1: valgrind ./syscall-restart1 syscall-restart2: valgrind ./syscall-restart2 system: valgrind ./system yield: valgrind ./yield -- Finished tests in none/tests ---------------------------------------- == 173 tests, 4 stderr failures, 0 stdout failures ================= helgrind/tests/deadlock (stderr) helgrind/tests/race (stderr) helgrind/tests/race2 (stderr) memcheck/tests/writev (stderr) make: *** [regtest] Error 1 |
|
From: Tom H. <th...@cy...> - 2004-07-18 02:08:18
|
Nightly build on standard ( Red Hat 7.2 ) started at 2004-07-18 03:00:02 BST Checking out source tree ... done Configuring ... done Building ... done Running regression tests ... done Last 20 lines of log.verbose follow rcrl: valgrind ./rcrl readline1: valgrind ./readline1 resolv: valgrind ./resolv rlimit_nofile: valgrind ./rlimit_nofile seg_override: valgrind ./seg_override sem: valgrind ./sem semlimit: valgrind ./semlimit sha1_test: valgrind ./sha1_test shortpush: valgrind ./shortpush shorts: valgrind ./shorts smc1: valgrind ./smc1 susphello: valgrind ./susphello syscall-restart1: valgrind ./syscall-restart1 syscall-restart2: valgrind ./syscall-restart2 system: valgrind ./system yield: valgrind ./yield -- Finished tests in none/tests ---------------------------------------- == 173 tests, 0 stderr failures, 0 stdout failures ================= |
|
From: Tom H. <th...@cy...> - 2004-07-18 02:08:13
|
Nightly build on alvis ( Red Hat 7.3 ) started at 2004-07-18 03:05:02 BST Checking out source tree ... done Configuring ... done Building ... done Running regression tests ... done Last 20 lines of log.verbose follow shortpush: valgrind ./shortpush shorts: valgrind ./shorts smc1: valgrind ./smc1 susphello: valgrind ./susphello syscall-restart1: valgrind ./syscall-restart1 syscall-restart2: valgrind ./syscall-restart2 system: valgrind ./system yield: valgrind ./yield -- Finished tests in none/tests ---------------------------------------- == 173 tests, 6 stderr failures, 1 stdout failure ================= addrcheck/tests/toobig-allocs (stderr) memcheck/tests/badjump (stderr) memcheck/tests/brk (stderr) memcheck/tests/error_counts (stdout) memcheck/tests/new_nothrow (stderr) memcheck/tests/toobig-allocs (stderr) memcheck/tests/writev (stderr) make: *** [regtest] Error 1 |