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
(17) |
2
(15) |
3
(36) |
4
(24) |
5
(36) |
|
6
(18) |
7
(16) |
8
(18) |
9
(19) |
10
(18) |
11
(37) |
12
(18) |
|
13
(13) |
14
(21) |
15
(27) |
16
(10) |
17
(16) |
18
(25) |
19
(21) |
|
20
(11) |
21
(14) |
22
(6) |
23
(15) |
24
(27) |
25
(3) |
26
(9) |
|
27
(16) |
28
(24) |
29
(21) |
30
(43) |
31
(42) |
|
|
|
From: <sv...@va...> - 2005-03-12 23:57:44
|
Author: sewardj Date: 2005-03-12 23:57:39 +0000 (Sat, 12 Mar 2005) New Revision: 73 Modified: trunk/devel/cvs_svn.html Log: Fix the anonymous checkout insns. Modified: trunk/devel/cvs_svn.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/devel/cvs_svn.html 2005-03-12 23:05:44 UTC (rev 72) +++ trunk/devel/cvs_svn.html 2005-03-12 23:57:39 UTC (rev 73) @@ -42,11 +42,18 @@ <a href=3D"http://svn.valgrind.org/">http://svn.valgrind.org/</a>.</p> =20 <p>To check out code on the 3.0 line (anonymous, read-only SVN=20 -access):<br /> -<code> svn co http://svn.valgrind.org/</code><br /> -To build the result, follow the instructions -in the <code>README</code> file that the checkout should give -you.</p> +access), proceed as follows. Note that=20 +the 3.0 line has been split into two pieces: Vex, a library that +provides dynamic translation services, and Valgrind proper. You=20 +need both pieces. Do this:<br /> +<code> svn co svn://svn.valgrind.org/vex/trunk</code><br /> +<code> svn co svn://svn.valgrind.org/valgrind/trunk</code><b= r /> +<code> cd vex/trunk && make clean version all</code><br /> +<code> cd valgrind/trunk</code><br /> +<code> ./autogen.sh</code><br /> +<code> ./configure --prefix=3D... --with-vex=3D/path/to/vex/= trunk</code><br /> +<code> make install</code><br /> +</p> =20 <p><b>Note:</b> as of mid March 2005, the 3.0 line has seen massive upheaval and so is majorly broken in various ways. We expect |
|
From: Dirk M. <dm...@gm...> - 2005-03-12 18:11:41
|
On Saturday 12 March 2005 05:33, Nicholas Nethercote wrote: > The website has moved! Hmm, you just could have told me.. The new website is not supposed to get mirrored under valgrind.kde.org ? we can do a CNAME on valgrind.org or do a permanent http redirect (for all urls under valgrind.kde.org, not just the main page), whatever fits the purpose better. Dirk |
|
From: Jeremy F. <je...@go...> - 2005-03-12 09:04:35
|
I have made 2.4.0.rc3 available for testing at http://www.goop.org/~jeremy/valgrind/dist/. Please test it out and report any problems at http://bugs.kde.org/enter_valgrind_bug.cgi . Changes since rc2 are: * Fix which prevents an assertion failure when a threaded program forks, and the child starts a thread. * Fix a problem in which signals which have the default action of "ignore" (SIGCONT, WINCH, USR and CHLD) interrupted a blocked syscall. For these signals, Valgrind doesn't set a signal handler unless the client needs one. * Remove segment merging from mprotect(), which was causing rtldi to trigger a Valgrind internal error. * Fix the parsing of the 'R' floating-point type in the stabs parser. The full set of changes since 2.2.0 is attached. J |
|
From: Jeremy F. <je...@go...> - 2005-03-12 08:56:30
|
CVS commit by fitzhardinge: Change version to 2.4.0.rc3 M +1 -1 configure.in 1.153 --- valgrind/configure.in #1.152:1.153 @@ -1,4 +1,4 @@ # Process this file with autoconf to produce a configure script. -AC_INIT(Valgrind, 2.4.0.rc2, val...@li...) +AC_INIT(Valgrind, 2.4.0.rc3, val...@li...) AC_CONFIG_SRCDIR(coregrind/vg_main.c) AM_CONFIG_HEADER(config.h) |
|
From: Jeremy F. <je...@go...> - 2005-03-12 08:22:42
|
CVS commit by fitzhardinge:
Fix incorrect parsing of 'R' floating-point types.
M +0 -2 vg_stabs.c 1.23
--- valgrind/coregrind/vg_stabs.c #1.22:1.23
@@ -679,6 +679,4 @@ static SymType *stabtype_parser(SegInfo
bytes = atoi(&p, 0);
EXPECT(';', "FP-TYPE bytes");
- atoi(&p, 0);
- EXPECT(';', "FP-TYPE extra");
type = VG_(st_mkfloat)(def, bytes);
|
|
From: Nicholas N. <nj...@cs...> - 2005-03-12 07:18:21
|
Hi,
I've received enough responses to the current survey that I know I want to
streamline it. Below, I explain which questions I want to cull and why.
Basically, the shorter the better, since excessive length will put some
people off.
Almost every question lets you put additional comments. I propose merging
some of these so there is just one comments box per section.
Also, the new website allows you to do this with a web form, or via email.
I propose removing the email option -- doesn't seem much point having both
methods.
It's worth noting that every question serves one of two basic goals:
obtain information that lets us improve Valgrind, or obtain information
that is just interesting to us. The first goal is crucial, the second
goal is less important.
My comments are in [[double square brackets]].
Any opinions are welcome; if I don't get any, I'll just go ahead and make
the changes.
N
------ Learning about Valgrind -------------------------------------
# How did you first learn about Valgrind?
from a friend [ ]
from a workmate [ ]
searching for tools [ ]
from a publication [ ] (eg. a mailing list;
please name under "comments")
other :
# How many other programmers have you told about Valgrind?
# How many of them have used it as a result?
# Any other comments about how you first learnt about Valgrind?
[[these ones not much use... but I might keep them...]]
------ Using Valgrind ----------------------------------------------
# Approximately how long (in months) have you been using Valgrind?
[[hmm, not sure, somewhat interesting, but not terrible useful... could be
cross-correlated with
other responses to indicate experience, if I wanted to get fancy...]]
# When developing, on what events do you *manually* run Valgrind?
# (Select all the options that are appropriate.)
after all changes [ ]
after big changes [ ]
before a release [ ]
when a bug occurs [ ]
when a bug is suspected [ ]
when optimising [ ]
just "now and then" [ ]
other :
# On average, approximately how often do you use Valgrind?
hourly [ ]
daily [ ]
weekly [ ]
monthly [ ]
other :
[[I suggest merging those two]]
# Do you use Valgrind in any automated fashion? (Eg. in a test
# suite, but *not* just by starting manually using a script.)
yes [ ]
no [ ]
Comments:
[[remove this, not much use]]
# What x86 machine(s) do you use Valgrind on? Estimate the
# proportion of your Valgrind usage on different machines.
# (Example: Pentium 4 70%, Athlon 30%)
# What Linux distribution(s) do you use Valgrind on?
# Estimate the proportion of your Valgrind usage on different
# distributions. Please give version numbers if possible.
# (Example: RedHat 9.0 90%, SuSe 8.1 10%)
[[these two interesting, keep]]
# In what form did you/do you obtain Valgrind?
# (Select all the options that are appropriate.)
source, from CVS [ ]
source, from website [ ]
pre-built version (eg. RPM) [ ]
already installed on system [ ]
other :
[[interesting, keep]]
# Which Valgrind tools do you use? Estimate the proportion of
# your Valgrind usage each tool accounts for.
# (Example: Memcheck 80%, Addrcheck 10%, Cachegrind 10%)
Memcheck :
Addrcheck :
Cachegrind :
Helgrind :
Calltree/KCachegrind :
Massif :
other :
[[crucial! keep]]
# Which of Valgrind's command-line flags do you always,
# or almost always, use?
# (Example: --leak-check=yes, --num-callers=20)
# Which of Valgrind's command-line flags do you sometimes use?
[[these two crucial! keep]]
# Any other comments about how you use Valgrind?
------ Comparing Valgrind with similar tools -----------------------
# Have you used other tools that are similar to any of the
# Valgrind tools?
yes [ ]
no [ ]
# If so, for each tool, please provide the following information.
# Take more than one line if necessary.
name of other tool :
hardware/OS platform : (eg. x86/Linux; Solaris/SPARC)
ways in which...
...Valgrind is better :
...Valgrind is worse :
...Valgrind is equal :
# Any other comments about how Valgrind compares with other tools?
[[remove this whole section. Basically, I originally put it there to get
comparisons against Purify. We now know that almost everyone thinks V is
as good or better. No point having it now.]]
------ Valgrind on other platforms ---------------------------------
# If Valgrind was available on all hardware/OS platforms,
# estimate what proportion of your usage would be on each
# platform. Please describe each platform as precisely as
# possible.
#
# Example answer:
# PowerPC/MacOS X : 50%
# SPARC9/Solaris : 25%
# x86/Linux : 20%
# IA64/Linux : 5%
x86/Linux :
[[Crucial! keep]]
------ Software issues ---------------------------------------------
# The following questions are about software issues,
# eg. Valgrind's licence, speed, memory usage, ease of use,
# quality of information produced, robustness, documentation, etc.
# List up to 3 existing features of Valgrind that you think are
# good. Give as much detail as necessary.
1.
2.
3.
# List up to 3 existing features of Valgrind that you think need
# improvement. Give as much detail as necessary.
1.
2.
3.
# List up to 3 missing features you would like added to Valgrind.
1.
2.
3.
# Do you have ideas/wishes for new tools that could be built with
# Valgrind? Give as much detail as necessary.
# Any other comments about software issues?
[[this whole section crucial, keep]]
------ Non-software issues -----------------------------------------
# The following questions are about non-software issues,
# eg. Valgrind's website, release frequency, bug handling,
# mailing lists, publicity, etc.
# List up to three aspects of Valgrind's development that you
# think are good. Give as much detail as necessary.
1.
2.
3.
# List up to three aspects of Valgrind's development that you
# think need improvement. Give as much detail as necessary.
1.
2.
3.
[[those two important, keep]]
# Have you submitted any bug reports or feature requests for
# Valgrind?
yes [ ]
no [ ]
Comments:
# Have you contributed any code that has been included in Valgrind?
yes [ ]
no [ ]
Comments:
[[remove these two. I don't even know why I put them in.]]
# Any other comments about the non-software issues?
------ Project details ---------------------------------------------
# For *each project* on which you have used Valgrind, we would be
# interested to know the following information. Omit any
# details you want to keep private. Please estimate for any
# answers you're unsure about. Take more than one line per
# answer if necessary.
project name :
website (if one exists):
brief description :
public or private? :
license : (eg. GNU GPL; BSD; proprietary)
language(s) : (estimate proportions if > 1,
eg. 80% C, 20% Fortran)
number of programmers:
- in total :
- using Valgrind :
size (lines of code) :
number of users :
development location :
other comments :
[[keep this, interesting]]
# Would you be willing to have your project mentioned on the
# Valgrind website as one that uses Valgrind? (Please only say
# "yes" if you have the appropriate authority within your project
# to do so, or you have asked someone with the appropriate
# authority.)
yes [ ]
no [ ]
[[keep this, useful fodder for the website users list. Make it clear
that we would only give the project name, web address, and a brief
description, but none of the other details.]]
# If so, please specify any information you gave in the previous
# answer that you do *not* want mentioned (eg. "don't mention the
# development location"). We will not mention your name.
[[remove this in light of change to previous question]]
------ Supporting Valgrind -----------------------------------------
# It costs you nothing to use Valgrind, but it costs us money to
# develop it. Would you be willing to donate money to support
# Valgrind's continued development? (This is a sensitive
# question; feel free to give no answer. If you answer "yes",
# quantitative comments would be appreciated.)
yes [ ]
no [ ]
no answer [ ]
Comments:
# Would you be willing to contribute to Valgrind in a
# non-monetary fashion? Please indicate what form this might
# take (eg. help with documentation).
[[remove this whole section; it's obnoxious and doesn't get useful
responses. The donations page is there on the website, people can
go via that if they want.]]
------ Surveys -----------------------------------------------------
# Any comments about the content, structure or results of this
# survey, or the previous survey?
[[keep this, useful]]
|
|
From: Bob R. <bo...@br...> - 2005-03-12 04:57:43
|
On Fri, Mar 11, 2005 at 10:42:15PM -0600, Nicholas Nethercote wrote: > > Hi, > > The Valgrind website has been totally overhauled, and moved. The new > address is: > > http://www.valgrind.org Great job on the new site! Do you think it would be to much of a hassle to redirect valgrind.org->www.valgrind.org? Bob Rossi |
|
From: Nicholas N. <nj...@cs...> - 2005-03-12 04:42:18
|
Hi, The Valgrind website has been totally overhauled, and moved. The new address is: http://www.valgrind.org Thanks to Donna Robinson for her wonderful job with this. Also, a new mailing list, valgrind-announce, has been created. You can sign up for it at: http://lists.sourceforge.net/lists/listinfo/valgrind-announce It will be a low-volume list that is used only for announcing new versions of Valgrind. N |
|
From: Nicholas N. <nj...@cs...> - 2005-03-12 04:34:07
|
CVS commit by nethercote: Hmm, try that again. M +0 -40 index.html 1.26 --- devel-home/valgrind/index.html #1.25:1.26 @@ -9,42 +9,2 @@ </body> </html> - -<!-- -<?php - $page_title = "A GPL'd system for debugging and profiling x86-Linux programs"; - $page_heading = "Latest News"; - include "header.inc" -?> - -<p class="news">August 31, 2004: A new stable release, <a -href="downloads.html">valgrind 2.2.0</a>, is available. 2.2.0 brings -many improvements over 2.0.0, and includes the new Massif -heap-profiling tool. - -<p class="news">March 04, 2004: An experimental PowerPC port is available. -See <a href="related.html">Related Projects</a>. -<hr> - -<p> -<strong>Valgrind is a GPL'd system for debugging and profiling x86-Linux -programs.</strong> - -With the tools that come with Valgrind, you can automatically detect -many memory management and threading bugs, avoiding hours of -frustrating bug-hunting, making your programs more stable. You can -also perform detailed profiling, to speed up and reduce memory use -of your programs. - -<p> -The Valgrind distribution includes five tools: two memory error -detectors, a thread error detector, a cache profiler and a heap -profiler. -Several other -tools have been built with Valgrind. -<p> -Use the menu at left to learn more. - -<?php - include "footer.inc" -?> ---> |
|
From: Nicholas N. <nj...@cs...> - 2005-03-12 04:33:07
|
CVS commit by nethercote: The website has moved! M +13 -1 index.html 1.25 --- devel-home/valgrind/index.html #1.24:1.25 @@ -1,2 +1,14 @@ +<html> +<body> +<center> +<h2>Valgrind, A GPL'd system for debugging and profiling x86-Linux programs</h2> +<p>March 12, 2005: Valgrind's home page has moved to +<a href="http://www.valgrind.org">http://www.valgrind.org</a>. +</p> +</center> +</body> +</html> + +<!-- <?php $page_title = "A GPL'd system for debugging and profiling x86-Linux programs"; @@ -36,3 +48,3 @@ include "footer.inc" ?> - +--> |
|
From: <js...@ac...> - 2005-03-12 04:02:08
|
Nightly build on phoenix ( SuSE 9.1 ) started at 2005-03-12 03:50:00 GMT Checking out source tree ... done Configuring ... done Building ... done Running regression tests ... done Last 20 lines of log.verbose follow insn_mmx: valgrind ./insn_mmx insn_mmxext: (skipping, prereq failed: ../../../tests/cputest x86-mmxext) insn_sse: valgrind ./insn_sse insn_sse2: (skipping, prereq failed: ../../../tests/cputest x86-sse2) int: valgrind ./int pushpopseg: valgrind ./pushpopseg rcl_assert: valgrind ./rcl_assert seg_override: valgrind ./seg_override -- Finished tests in none/tests/x86 ------------------------------------ yield: valgrind ./yield -- Finished tests in none/tests ---------------------------------------- == 200 tests, 5 stderr failures, 0 stdout failures ================= memcheck/tests/pth_once (stderr) memcheck/tests/scalar (stderr) memcheck/tests/threadederrno (stderr) memcheck/tests/writev (stderr) corecheck/tests/fdleak_fcntl (stderr) make: *** [regtest] Error 1 |
|
From: Tom H. <to...@co...> - 2005-03-12 03:28:15
|
Nightly build on dunsmere ( Fedora Core 3 ) started at 2005-03-12 03:20:03 GMT Checking out source tree ... done Configuring ... done Building ... done Running regression tests ... done Last 20 lines of log.verbose follow insn_cmov: valgrind ./insn_cmov insn_fpu: valgrind ./insn_fpu insn_mmx: valgrind ./insn_mmx insn_mmxext: valgrind ./insn_mmxext insn_sse: valgrind ./insn_sse insn_sse2: (skipping, prereq failed: ../../../tests/cputest x86-sse2) int: valgrind ./int sh: line 1: 10160 Segmentation fault VALGRINDLIB=/tmp/valgrind.17512/valgrind/.in_place /tmp/valgrind.17512/valgrind/./coregrind/valgrind --command-line-only=yes --memcheck:leak-check=no --addrcheck:leak-check=no --tool=none ./int >int.stdout.out 2>int.stderr.out pushpopseg: valgrind ./pushpopseg rcl_assert: valgrind ./rcl_assert seg_override: valgrind ./seg_override -- Finished tests in none/tests/x86 ------------------------------------ yield: valgrind ./yield -- Finished tests in none/tests ---------------------------------------- == 206 tests, 2 stderr failures, 0 stdout failures ================= memcheck/tests/scalar (stderr) memcheck/tests/scalar_supp (stderr) make: *** [regtest] Error 1 |
|
From: Tom H. <th...@cy...> - 2005-03-12 03:22:16
|
Nightly build on audi ( Red Hat 9 ) started at 2005-03-12 03:15:01 GMT Checking out source tree ... done Configuring ... done Building ... done Running regression tests ... done Last 20 lines of log.verbose follow cpuid: valgrind ./cpuid dastest: valgrind ./dastest fpu_lazy_eflags: valgrind ./fpu_lazy_eflags insn_basic: valgrind ./insn_basic insn_cmov: valgrind ./insn_cmov insn_fpu: valgrind ./insn_fpu insn_mmx: valgrind ./insn_mmx insn_mmxext: valgrind ./insn_mmxext insn_sse: valgrind ./insn_sse insn_sse2: (skipping, prereq failed: ../../../tests/cputest x86-sse2) int: valgrind ./int pushpopseg: valgrind ./pushpopseg rcl_assert: valgrind ./rcl_assert seg_override: valgrind ./seg_override -- Finished tests in none/tests/x86 ------------------------------------ yield: valgrind ./yield -- Finished tests in none/tests ---------------------------------------- == 205 tests, 0 stderr failures, 0 stdout failures ================= |
|
From: Tom H. <th...@cy...> - 2005-03-12 03:16:30
|
Nightly build on ginetta ( Red Hat 8.0 ) started at 2005-03-12 03:10:01 GMT Checking out source tree ... done Configuring ... done Building ... done Running regression tests ... done Last 20 lines of log.verbose follow insn_basic: valgrind ./insn_basic insn_cmov: valgrind ./insn_cmov insn_fpu: valgrind ./insn_fpu insn_mmx: valgrind ./insn_mmx insn_mmxext: valgrind ./insn_mmxext insn_sse: valgrind ./insn_sse insn_sse2: (skipping, prereq failed: ../../../tests/cputest x86-sse2) int: valgrind ./int pushpopseg: valgrind ./pushpopseg rcl_assert: valgrind ./rcl_assert seg_override: valgrind ./seg_override -- Finished tests in none/tests/x86 ------------------------------------ yield: valgrind ./yield -- Finished tests in none/tests ---------------------------------------- == 204 tests, 2 stderr failures, 0 stdout failures ================= memcheck/tests/pth_once (stderr) memcheck/tests/threadederrno (stderr) make: *** [regtest] Error 1 |
|
From: Tom H. <th...@cy...> - 2005-03-12 03:15:32
|
Nightly build on standard ( Red Hat 7.2 ) started at 2005-03-12 03:00:02 GMT Checking out source tree ... done Configuring ... done Building ... done Running regression tests ... done Last 20 lines of log.verbose follow insn_mmx: valgrind ./insn_mmx insn_mmxext: valgrind ./insn_mmxext insn_sse: valgrind ./insn_sse insn_sse2: (skipping, prereq failed: ../../../tests/cputest x86-sse2) int: valgrind ./int pushpopseg: valgrind ./pushpopseg rcl_assert: valgrind ./rcl_assert seg_override: valgrind ./seg_override -- Finished tests in none/tests/x86 ------------------------------------ yield: valgrind ./yield -- Finished tests in none/tests ---------------------------------------- == 204 tests, 5 stderr failures, 0 stdout failures ================= memcheck/tests/leak-tree (stderr) memcheck/tests/pth_once (stderr) memcheck/tests/threadederrno (stderr) memcheck/tests/vgtest_ume (stderr) addrcheck/tests/leak-tree (stderr) make: *** [regtest] Error 1 |
|
From: Tom H. <th...@cy...> - 2005-03-12 03:11:38
|
Nightly build on alvis ( Red Hat 7.3 ) started at 2005-03-12 03:05:01 GMT Checking out source tree ... done Configuring ... done Building ... done Running regression tests ... done Last 20 lines of log.verbose follow -- Finished tests in none/tests ---------------------------------------- == 204 tests, 15 stderr failures, 0 stdout failures ================= memcheck/tests/addressable (stderr) memcheck/tests/describe-block (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/pointer-trace (stderr) memcheck/tests/pth_once (stderr) memcheck/tests/threadederrno (stderr) memcheck/tests/vgtest_ume (stderr) addrcheck/tests/leak-0 (stderr) addrcheck/tests/leak-cycle (stderr) addrcheck/tests/leak-regroot (stderr) addrcheck/tests/leak-tree (stderr) make: *** [regtest] Error 1 |
|
From: Jeremy F. <je...@go...> - 2005-03-12 00:52:10
|
CVS commit by fitzhardinge:
Don't merge segments after mprotect. This was the only change needed
to make rtldi work.
M +1 -1 vg_memory.c 1.95
--- valgrind/coregrind/vg_memory.c #1.94:1.95
@@ -520,5 +520,5 @@ void VG_(mprotect_range)(Addr a, SizeT l
}
- merge_segments(a, len);
+ //merge_segments(a, len);
}
|
|
From: Jeremy F. <je...@go...> - 2005-03-12 00:24:02
|
CVS commit by fitzhardinge:
For signals which are ignored by default (SIGCONT, CHLD, WINCH and URG),
don't set a signal handler unless the client has. This prevents syscalls
from being spuriously interrupted if one if these signals is received.
BUGS: 101313
M +9 -2 vg_signals.c 1.139
--- valgrind/coregrind/vg_signals.c #1.138:1.139
@@ -252,6 +252,11 @@ void calculate_SKSS_from_SCSS ( SKSS* ds
case VKI_SIGCONT:
- /* Let the kernel handle SIGCONT unless the client is actually
- catching it. */
+ case VKI_SIGCHLD:
+ case VKI_SIGWINCH:
+ case VKI_SIGURG:
+ /* For signals which are have a default action of Ignore,
+ only set a handler if the client has set a signal handler.
+ Otherwise the kernel will interrupt a syscall which
+ wouldn't have otherwise been interrupted. */
if (vg_scss.scss_per_sig[sig].scss_handler == VKI_SIG_DFL)
skss_handler = VKI_SIG_DFL;
@@ -263,4 +268,6 @@ void calculate_SKSS_from_SCSS ( SKSS* ds
default:
+ /* VKI_SIGVG* are runtime variables, so we can't make them
+ switch cases */
if (sig == VKI_SIGVGKILL)
skss_handler = sigvgkill_handler;
|