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
|
2
(13) |
3
(29) |
|
4
(18) |
5
(12) |
6
(12) |
7
(22) |
8
(9) |
9
(14) |
10
(6) |
|
11
|
12
|
13
(1) |
14
(5) |
15
(11) |
16
(7) |
17
(5) |
|
18
(1) |
19
(8) |
20
(7) |
21
(12) |
22
(5) |
23
(17) |
24
(6) |
|
25
(27) |
26
(17) |
27
(2) |
28
(10) |
29
(3) |
30
(8) |
31
(20) |
|
From: Nicholas N. <nj...@ca...> - 2004-01-31 23:09:11
|
On Mon, 26 Jan 2004, Robert Walsh wrote: > > Should the FD returned by epoll_create() be recorded for the FD tracking > > code? > > If it creates an FD visible to user code, then yes. Ok, third time lucky... One thing I wasn't sure about: do I need to include a call to fd_allowed()? Not every call to record_fd_opened() is preceded by one (eg. fcntl()), although most are... maybe the missing ones are oversights? N |
|
From: Nicholas N. <nj...@ca...> - 2004-01-31 22:58:06
|
On Fri, 30 Jan 2004, Nicholas Nethercote wrote:
> I imagined this:
>
> common user options for all Valgrind tools, with defaults in [ ]:
> --tool=<name> Use the Valgrind tool named <name>
> --help show this message
> * --help-debug show this message, plus debugging options
Ok, that's done. However, there are still too many options, mostly
because of the uncommon options:
uncommon user options for all Valgrind tools:
--run-libc-freeres=no|yes Free up glibc memory at exit? [yes]
--weird-hacks=hack1,hack2,... [none]
recognised hacks are: ioctl-VTIME truncate-writes lax-ioctls
--signal-polltime=<time> time, in mS, we should poll for signals.
Only applies for older kernels which need
signal routing [50]
--lowlat-signals=no|yes improve wake-up latency when a thread receives
a signal [no]
--lowlat-syscalls=no|yes improve wake-up latency when a thread's
syscall completes [no]
--pointercheck=no|yes enforce client address space limits [yes]
Since they're all 0.1% cases, I think it would be nice to move all of them
into --weird-hacks (except --signal-polltime, which is hard to do since it
is not a boolean), eg:
uncommon user options for all Valgrind tools:
--weird-hacks=hack1,hack2,... [none]
recognised hacks are: ioctl-VTIME, truncate-writes, lax-ioctls,
libc-freeres, lowlat-sigs, lowlat-syscalls, no-ptrcheck
--signal-polltime=<time> time, in mS, we should poll for signals.
Only applies for older kernels which need
signal routing [50]
Of course, for backwards compatibility, we could let the old invocations
still work. The way --weird-hacks works internally would have to be
changed slightly, eg. into a bit-mask, because it currently only allows
one weird hack at a time.
Comments?
N
|
|
From: Nicholas N. <nj...@ca...> - 2004-01-31 22:55:20
|
CVS commit by nethercote:
No longer showing debugging options for --help; only for the newly added
--help-debug.
M +24 -18 vg_main.c 1.143
M +4 -0 docs/coregrind_core.html 1.25
--- valgrind/coregrind/vg_main.c #1.142:1.143
@@ -1353,5 +1353,5 @@ static void load_tool( const char *tooln
static void load_client(char* cl_argv[], const char* exec,
- /*inout*/Bool* need_help,
+ /*inout*/Int* need_help,
/*out*/struct exeinfo* info, /*out*/Addr* client_eip)
{
@@ -1362,5 +1362,5 @@ static void load_client(char* cl_argv[],
( NULL == (exec = find_executable(cl_argv[0])) ) )
{
- *need_help = True;
+ *need_help = 1;
}
}
@@ -1470,5 +1470,5 @@ static void config_error ( Char* msg )
}
-void usage ( void )
+void usage ( Bool debug_help )
{
Char* usage1 =
@@ -1478,4 +1478,5 @@ void usage ( void )
" --tool=<name> Use the Valgrind tool named <name>\n"
" --help show this message\n"
+" --help-debug show this message, plus debugging options\n"
" --version show version\n"
" -q --quiet run silently; only print error msgs\n"
@@ -1558,4 +1559,5 @@ void usage ( void )
VG_(printf)(" (none)\n");
}
+ if (debug_help) {
VG_(printf)(usage2);
@@ -1568,4 +1570,5 @@ void usage ( void )
VG_(printf)(" (none)\n");
}
+ }
VG_(printf)(usage3, VG_BUGS_TO);
@@ -1577,5 +1580,5 @@ void usage ( void )
static void pre_process_cmd_line_options
- ( Bool* need_help, const char** tool, const char** exec )
+ ( Int* need_help, const char** tool, const char** exec )
{
UInt i;
@@ -1589,5 +1592,8 @@ static void pre_process_cmd_line_options
} else if (strcmp(VG_(vg_argv)[i], "--help") == 0) {
- *need_help = True;
+ *need_help = 1;
+
+ } else if (strcmp(VG_(vg_argv)[i], "--help-debug") == 0) {
+ *need_help = 2;
} else if (strncmp(VG_(vg_argv)[i], "--tool=", 7) == 0 ||
@@ -1604,5 +1610,5 @@ static void pre_process_cmd_line_options
if (!need_help)
list_tools();
- usage();
+ usage(/*help-debug?*/False);
}
}
@@ -1610,5 +1616,5 @@ static void pre_process_cmd_line_options
static void process_cmd_line_options
( UInt* client_auxv, Addr esp_at_startup,
- const char* toolname, Bool need_help )
+ const char* toolname, Int need_help )
{
Int i, eventually_logfile_fd;
@@ -1639,5 +1645,5 @@ static void process_cmd_line_options
if (need_help)
- usage();
+ usage(/*--help-debug?*/need_help == 2);
/* We know the initial ESP is pointing at argc/argv */
@@ -1877,5 +1883,5 @@ static void process_cmd_line_options
else if ( ! VG_(needs).command_line_options
|| ! SK_(process_cmd_line_option)(arg) ) {
- usage();
+ usage(/*--help-debug?*/need_help == 2);
}
}
@@ -2689,5 +2695,5 @@ int main(int argc, char **argv)
char *preload; /* tool-specific LD_PRELOAD .so */
char **env;
- Bool need_help = False;
+ Int need_help = 0; // 0 = no, 1 = --help, 2 = --help-debug
struct exeinfo info;
ToolInfo *toolinfo = NULL;
--- valgrind/coregrind/docs/coregrind_core.html #1.24:1.25
@@ -496,4 +496,8 @@
selected tool. </li><br><p>
+ <li><code>--help-debug</code><br>
+ <p>Same as <code>--help</code>, but also lists debugging options which
+ usually are only of use to developers.</li><br><p>
+
<li><code>--version</code><br> <p>Show the version number of the
Valgrind core. Tools can have their own version numbers. There
|
|
From: Nicholas N. <nj...@ca...> - 2004-01-31 22:30:32
|
CVS commit by nethercote:
Totally rewrote new survey. Much more precise and detailed; responses should
give us much better information, that can be more directly acted upon.
Updated survey-response and surveys.html a little.
M +15 -1 survey-response 1.2
M +191 -240 survey2 1.4
M +7 -8 surveys.html 1.4
--- devel-home/valgrind/survey-response #1.1:1.2
@@ -8,5 +8,5 @@
- better overview makes it clearer what Valgrind is, that is has multiple
tools, etc
- - added links to external skins, GUIs, CVS repository, etc
+ - added links to external tools, GUIs, CVS repository, etc
- bugzilla setup for bugs, feature requests
@@ -14,4 +14,13 @@
- started phasing out the term "skin", using "tool" instead -- not using
"skin" on website anymore
+ - eventually, there will be no default tool, so that users are forced to
+ realise that Valgrind is more than just Memcheck. Users will be allowed
+ to specify their own default tool in a .valgrindrc file.
+
+features:
+ - 2.1.1 can run statically linked binaries.
+
+development:
+ - Bugzilla pages should ensure bug fixes and patches are not forgotten
releases:
@@ -20,2 +29,7 @@
error messages:
- small improvements made so far, will be seen in 2.1 series
+
+surveys:
+ - better version of survey written; information from responses should be
+ much more focused, and directly applicable to understanding how Valgrind is
+ used, and how to improve it.
--- devel-home/valgrind/survey2 #1.3:1.4
@@ -1,331 +1,289 @@
#----------------------------------------------------------------------------
-# Valgrind survey:
+# Valgrind survey
#----------------------------------------------------------------------------
# General instructions:
-# - You can ignore questions you don't like, eg. if you want to keep things
-# confidential.
+# - Please estimate if you are unsure about any answers.
#
-# - We won't make raw data public, only summaries. Some summary information
-# might make it obvious that you've replied, eg. if you are the only developer
-# on a project; if you want , tell us and we won't make the incriminating
-# knowledge public (eg. "I work on a C++ library", rather than "I work on the
-# XYZ C++ library".)
+# - Most questions have a "comments" field for extra comments.
#
-# - We have no plans to make Valgrind commercial. The questions are detailed
-# just because we are interested in seeing how Valgrind is used.
-
-
-#----------------------------------------------------------------------------
-# Project types
-#----------------------------------------------------------------------------
-# For each project on which you have used Valgrind tools, please provide
-# the following information.
-#
-# Omit any details you don't want us to know. Please give estimates for
-# things you're not sure about. Take more than one line per answer if
-# necessary.
+# - Your response is confidential; we won't make raw data public, only
+# summaries. The only exception to this is if you answer "yes" to the
+# question below about mentioning your project on the Valgrind website.
#
-# Example answers:
-# name : eg. myprogram
-# description : eg. telecom app; strategy game; C compiler
-# website : eg. www.myprogram.org; none
-# development location : eg. United Kingdom; world-wide
-# number of users : eg. myself; about 20; thousands
-# type of users : eg. programmers; musicians; office workers
-# how released : eg. commercial; open source; personal use only
-# language(s) : eg. C; C++; 80% C and 20% Fortran
-# size (LOC) : eg. 500 LOC; 100 KLOC; 2 MLOC
-# programmers
-# total : eg. 1; 3; about 20
-# using Valgrind tools : eg. 1; 2; about 5
-# number using Valgrind : eg. 1; 5
-# any other information :
-
-name :
-description :
-website :
-development location :
-number of users :
-type of users :
-how released :
-language(s) :
-size (LOC) :
-programmers
- total :
- using Valgrind tools :
-any other information :
-
+# - We have no plans to commercialize Valgrind. You can relax, that's not what
+# this is about.
#----------------------------------------------------------------------------
-# Using Valgrind tools
+# Learning about Valgrind
#----------------------------------------------------------------------------
-# What Linux distribution(s) do you use Valgrind tools on (please give
-# version numbers if possible, eg. RedHat 9.0, SuSe 8.1)
-
+# How did you first learn about Valgrind?
-
-# Please indicate what proportion of your total Valgrind use each skin accounts
-# for. Leave blank tools you never use. (Example: Memcheck 80%,
-# Addrcheck 10%, Cachegrind 10%)
-
-Memcheck :
-Addrcheck :
-Cachegrind :
-Helgrind :
-Calltree/KCachegrind :
-Massif :
-Annelid :
-Crocus :
-VGProf :
+from a friend [ ]
+from a workmate [ ]
+from a publication [ ] (eg. a mailing list; please name under "comments")
+searching for tools [ ]
other :
-# When developing, on what events do you _manually_ run Valgrind tools?
-# (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 : [ ]
-other :
-
-# Do you use Valgrind tools in any automated fashion? If so, how?
-# (Select all the options that are appropriate.)
-
-no : [ ]
-in regression tests : [ ]
-in unit tests : [ ]
-in integration tests : [ ]
-in system tests : [ ]
-other :
+comments:
-# On average, approximately how often do you use Valgrind tools?
+# How many other programmers have you told about Valgrind?
+# How many of them have used it as a result?
-hourly : [ ]
-daily : [ ]
-weekly : [ ]
-monthly : [ ]
-other :
-# Any other comments about how you run Valgrind tools?
+comments:
+# Any other comments about your first use of Valgrind?
#----------------------------------------------------------------------------
-# Comparison with similar tools
+# Using Valgrind
#----------------------------------------------------------------------------
-# Have you used other tools that do similar things to Valgrind tools?
+# Approximately how long (in months) have you been using Valgrind?
-# If not, why not? (Select all the options that are appropriate.)
-too expensive : [ ]
-not available on my platform : [ ]
-don't know any similar tools : [ ]
-no particular reason : [ ]
-other :
+comments:
-# If so, for each tool, please provide the following information.
-#
-# Example answer:
-# other tool : FruityDebugger
-# platform : Solaris/SPARC
-# similar Valgrind tool : Memcheck
-# pros of Valgrind tool : Free, open source, runs on Linux. No
-# recompilation required. Faster.
-# cons of Valgrind tool : No GUI, error messages are harder to
-# understand. Can check stack variables.
-# tools are equal on : Find similar range of bugs.
-# other comments : If Memcheck was available on Solaris/SPARC,
-# I would not use FruityDebugger.
-
-other tool :
-platform :
-similar Valgrind tool :
-pros of Valgrind tool :
-cons of Valgrind tool :
-tools are equal on :
-other comments :
+# When developing, on what events do you *manually* run Valgrind?
+# (Select all the options that are appropriate.)
-# Any other comments about Valgrind in comparison with other tools?
+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 :
+comments:
+# On average, approximately how often do you use Valgrind?
-#----------------------------------------------------------------------------
-# Software issues
-#----------------------------------------------------------------------------
-# For each of the following software issues, please rate from 1--5 how happy
-# you are with it, where 1 == very unhappy, and 5 == very happy. Please add
-# any extra comments that are relevant after each issue.
+hourly [ ]
+daily [ ]
+weekly [ ]
+monthly [ ]
+other :
-# GPL Licence:
+comments:
+# Do you use Valgrind in any automated fashion? (Eg. in a test suite, but
+# *not* just by starting manually using a script.)
+yes [ ]
+no [ ]
-# Performance:
+comments:
+# 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%)
-# Ease of use (starting up):
+comments:
+# 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%)
-# Ease of use (interface):
+comments:
+# 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 :
+Annelid :
+other :
-# Quality of information found (error messages, etc):
+comments:
+# Which of Valgrind's command-line flags you always, or almost always, use?
+# (Example: --leak-check=yes, --num-callers=20)
-# Robustness
+comments:
+# Which of Valgrind's command-line flags you sometimes use?
-# Documentation:
+comments:
+# Any other comments about how you use Valgrind?
#----------------------------------------------------------------------------
-# Are there any software features that you think are particularly good?
+# Comparing Valgrind with similar tools
+#----------------------------------------------------------------------------
+# Have you used other tools that are similar to any of the Valgrind tools?
+yes [ ]
+no [ ]
+comments:
-# Are there any software features that you think are particularly bad?
+# 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 :
+comments:
-# Are there any software features that are missing and you would particularly
-# like? Please rate the importance of each one as low, medium, or high. (Nb:
-# please put any comments about porting Valgrind to other platforms in the
-# "Other platforms" section below).
+# Any other comments about how Valgrind compares with other tools?
+#----------------------------------------------------------------------------
+# 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%
-# Any other comments about the software?
+x86/Linux :
+comments:
#----------------------------------------------------------------------------
-# Non-software issues
+# Software issues
#----------------------------------------------------------------------------
-# For each of the following non-software issues, please rate from 1--5 how
-# happy with how each one is handled, where 1 == very unhappy, and
-# 5 == very happy. Please add any extra comments that are relevant after each
-# issue.
-
-# Frequency of releases:
+# 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.
-# Bug reporting/fixing
+1.
+2.
+3.
+# List up to 3 missing features you would like added to Valgrind.
+1.
+2.
+3.
-# Feature requests:
+# 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?
-# Valgrind mailing lists (if you read any of them):
+#----------------------------------------------------------------------------
+# 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.
-# Website:
+# List up to three aspects of Valgrind's development that you think need
+# improvement. Give as much detail as necessary.
+1.
+2.
+3.
+# Have you submitted any bug reports or feature requests for Valgrind?
-#----------------------------------------------------------------------------
-# Are there any development aspects that you think are particularly good?
+yes [ ]
+no [ ]
+comments:
+# Have you contributed any code that has been included in Valgrind?
-# Are there any development aspects that you think are particularly bad?
+yes [ ]
+no [ ]
+comments:
+# Any other comments about the non-software issues?
-# Any other comments about the development?
#----------------------------------------------------------------------------
-# Other platforms
+# Project details
#----------------------------------------------------------------------------
-# Would you find it useful if Valgrind was available on other platforms?
-# If Valgrind was available on all platforms, please indicate what
-# proportion of your usage would be on each platform. If you aren't sure,
-# please estimate. Please be as specific with your platform description as
-# possible.
-#
-# Example answer:
-# PowerPC/MacOS X : 50%
-# SPARC9/Solaris : 25%
-# x86/Linux : 20%
-# IA64/Linux : 5%
-
-x86/Linux :
-
-# For each platform (other than x86/Linux) mentioned in the previous
-# question, please indicate how much having Valgrind tools on that
-# platform will help _you_, using the following ratings:
-#
-# high: Would give you something the x86/Linux version cannot. Eg:
-# - part of your program(s) doesn't run on x86/Linux, or
-# - you ported your program to x86/Linux just to use Valgrind, or
-# - you have other programs that don't run on x86/Linux on which
-# you want to use Valgrind tools.
-#
-# medium: You would use it often, but it wouldn't give any big advantage
-# over the x86/Linux version. Eg. your program works on
-# multiple operating systems, and the Linux version isn't very
-# different to the other versions.
-#
-# low: You might use it, or use it only occasionally.
-#
-# Please add any explaining comments you think are relevant.
-#
-# Example answer:
-# PowerPC/MacOS X : medium, my main project has a MacOS X port
-# SPARC9/Solaris : high, I have several SPARC9/Solaris-only programs that
-# I can't port to other platforms
-# IA64/Linux : low, I might port to it if it becomes popular
-
+# 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 :
-# What platforms do you think other people would want? Please accompany each
-# one with a high, medium, or low ranking for importance.
+# 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 [ ]
-# Any other comments about porting Valgrind to other platforms?
+comments:
+# 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").
#----------------------------------------------------------------------------
-# Publicity
+# Supporting Valgrind
#----------------------------------------------------------------------------
-# How did you learn about Valgrind? (Select all options that are
-# appropriate.)
-
-from a friend : [ ]
-from a workmate : [ ]
-on the web:
- by luck : [ ]
- searching for tools : [ ]
-other :
-
-# How many other programmers have you told about 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:
-# How many of them have used it as a result?
-
-
-
-# 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.
-
-yes : [ ]
-no : [ ]
-
-# Any other comments about publicity matters?
-
+# Would you be willing to contribute to Valgrind in a non-monetary fashion?
+# Please indicate what form this might take (eg. help with documentation).
@@ -333,22 +291,11 @@
# Surveys
#----------------------------------------------------------------------------
-# Any comments about the previous survey, or this survey? (Eg. suggestions for
-# extra questions.)
-
+# Any comments about the content, structure or results of this survey, or
+# the previous survey?
#----------------------------------------------------------------------------
-# Thank you for your time.
-#
# Please send completed surveys to njn25 at cam dot ac dot uk.
-
-#----------------------------------------------------------------------------
-# Change log
+#
+# Thank you for your time and support.
#----------------------------------------------------------------------------
-$Log$
-Revision 1.3 2003/12/04 15:18:43 nethercote
-Added "Would you be willing to have your project mentioned on the Valgrind
-website" publicity question.
-
-
-Dec 3: added "before a release" option
--- devel-home/valgrind/surveys.html #1.3:1.4
@@ -6,8 +6,8 @@
<h3>Current Survey</h3>
-Let your opinions about Valgrind be heard: complete our current
-<a href="survey2">survey</a>. This survey is an improved and more detailed
-compared to our last survey. Even if you filled out the last survey, we'd like
-your response to this survey.
+Let your opinions about Valgrind be heard: complete our current
+<a href="survey2">survey</a>. Even if you completed the last survey, we'd like
+your response to this survey, as it will give us more precise and directly
+useful information.
<p>
Survey responses tell us what is good and bad about Valgrind, sate our
@@ -21,9 +21,8 @@
Thanks to all those who responded.
<p>
-Read the <a href="survey-summary">summary</a>, and a list of
+Read the <a href="survey-summary">summary</a>, and a list of some
<a href="survey-response">actions</a> we've taken in direct response to the
-survey results. Please note that this list only shows things we have done so
-far. We are continuing to address the issues raised by the survey; this takes
-time.
+survey results. Please note that this list does not show everything we've
+done, and we continue to address the issues raised.
<p>
|
|
From: Nicholas N. <nj...@ca...> - 2004-01-31 21:49:46
|
CVS commit by nethercote: Reworded M +15 -5 surveys.html 1.3 --- devel-home/valgrind/surveys.html #1.2:1.3 @@ -5,6 +5,19 @@ ?> -In November 2003, we ran a survey, and got 114 responses. Thanks to all those -who responded. +<h3>Current Survey</h3> +Let your opinions about Valgrind be heard: complete our current +<a href="survey2">survey</a>. This survey is an improved and more detailed +compared to our last survey. Even if you filled out the last survey, we'd like +your response to this survey. +<p> +Survey responses tell us what is good and bad about Valgrind, sate our +curiosity about how it is used, and encourage us to continue our efforts. +By completing the survey, you are supporting Valgrind. +<p> + +<h3>Previous Surveys</h3> +We ran our first survey in November 2003. The 116 responses gave us a huge +amount of information, and taught us a great deal about how Valgrind is used. +Thanks to all those who responded. <p> Read the <a href="survey-summary">summary</a>, and a list of @@ -14,7 +27,4 @@ time. <p> -We also have a <a href="survey2">second survey</a>. It's similar to the first, -but goes into more detail, taking on board the lessons we learnt from the first -survey. Fill it out to let us know what you think of Valgrind. <?php |
|
From: Nicholas N. <nj...@ca...> - 2004-01-31 21:49:13
|
CVS commit by nethercote: Mentioned mirroring of valgrind-users at Gmane. M +23 -14 lists.html 1.4 --- devel-home/valgrind/lists.html #1.3:1.4 @@ -5,18 +5,27 @@ ?> -The <a HREF="http://lists.sourceforge.net/lists/listinfo/valgrind-users"> -users list</a> is a general discussion list for anything that comes up -when using Valgrind -- if you can't work out how to use it, if you don't -understand an error message, you have an idea for a new Valgrind tool -and want some feedback, etc. It is read by all the developers, plus a -bunch of other knowledgeable folk. -<p> -The <a HREF="http://lists.sourceforge.net/lists/listinfo/valgrind-developers"> -developers list</a> is aimed at developers. It's for discussion of -technical implementation details. Our CVS commit logs are also emailed -there. -<p> -We hope to have an low-volume announcement list, for announcing new -releases, soon. +<ul> +<li>The + <a href="http://lists.sourceforge.net/lists/listinfo/valgrind-users">users + list</a> is a general discussion list for anything that comes up when using + Valgrind -- if you can't work out how to use it, if you don't understand an + error message, you have an idea for a new Valgrind tool and want some + feedback, etc. It is read by all the developers, plus a bunch of other + knowledgeable folk. + <p> + The list is mirrored at + <a href="http://news.gmane.org/gmane.comp.debugging.valgrind">Gmane</a>. + You can <a href="http://search.gmane.org">search</a> through old messages + using the group name <code>gmane.comp.debugging.valgrind</code>. + <p> +<li>The + <a href="http://lists.sourceforge.net/lists/listinfo/valgrind-developers">developers + list</a> is aimed at developers. It's for discussion of technical + implementation details. Our CVS commit logs are also emailed there. + <p> +</ul> + +We should really also have a low-volume announcement list, for announcing new +releases. <p> |
|
From: Nicholas N. <nj...@ca...> - 2004-01-31 19:27:46
|
CVS commit by nethercote: Added QSDK, Cactus M +7 -0 users.html 1.23 --- devel-home/valgrind/users.html #1.22:1.23 @@ -131,4 +131,7 @@ <dd>Numerical libraries for linear finite elements in two dimensions. +<dt><a href="http://www.cactuscode.org">Cactus</a> +<dd>A framework for parallel computation and collaborative code development. + <dt><a href="http://www.harmonyware.com">HarmonyWare</a> <dd>NURBS-based geometry translator tools. @@ -233,4 +236,8 @@ <dt><a href="http://www.scummvm.org">ScummVM</a> <dd>A virtual machine for classic graphical adventure games. + +<dt><a href="http://www.qubesoft.com/q/engine.php">QSDK</a> +<dd>A high performance cross platform game engine for Windows, Linux, + PS2 and XBox. Free for non-console development. </dl> |
|
From: Nicholas N. <nj...@ca...> - 2004-01-31 06:16:56
|
CVS commit by nethercote:
Added Yahoo! Messenger. Added more categories, moved some around a bit.
M +50 -39 users.html 1.15
--- devel-home/valgrind/users.html #1.14:1.15
@@ -14,4 +14,11 @@
of bugs found.)
+<dt><a href="http://www.lysator.liu.se/~alla/dia/">Dia</a>
+<dd>Diagram creator, particularly suited to drawing simple circuit diagrams,
+ and more.
+</dl>
+
+<h3>KDE</h3>
+<dl>
<dt><a href="http://www.kde.org">KDE</a>
<dd>Open Source graphical desktop environment for Unix workstations.
@@ -23,4 +30,10 @@
<dd>A web browser, file manager, and universal document viewing application.
+<dt><a href="http://www.trolltech.com/products/qt/">Qt by Trolltech</a>
+<dd>A multi-platform, C++ application development framework.
+</dl>
+
+<h3>GNOME</h3>
+<dl>
<dt><a href="http://www.gnome.org">GNOME</a>
<dd>A desktop environment and developer platform for Unix and Linux systems.
@@ -32,7 +45,10 @@
<dd>Integrated email, calendar, scheduling, contact management and
task-list system.
+
+<dt><a href="http://xmlsoft.org/">libxml2/libxslt</a>
+<dd>GNOME's multi-platform XML C parser and toolkit.
</dl>
-<h3>Web</h3>
+<h3>Web, Internet and Email</h3>
<dl>
<dt><a href="http://www.mozilla.org">Mozilla</a>
@@ -48,9 +64,19 @@
<dd>A small extensible web browser for internet appliances.
+<dt><a href="http://messenger.yahoo.com/messenger/download/unix.html">Yahoo! Messenger</a>
+<dd>A free instant messaging service.
+
+<dt><a href="http://pan.rebelbase.com">Pan</a>
+<dd>A newsreader supporting offline newsreading, article filtering, and
+ multiple connections.
+
+<dt><a href="http://www.pldaniels.com/ripmime">ripMIME</a>
+<dd>Email decoding engine and library.
+
<dt><a href="http://bidwatcher.sf.net">Bidwatcher</a>
<dd>An eBay auction listing tracker.
</dl>
-<h3>Databases</h3>
+<h3>Databases and Search Engines</h3>
<dl>
<dt><a href="http://www.mysql.com">MySQL</a>
@@ -72,4 +98,8 @@
dbAppliance</a>
<dd>Database performance monitoring and acceleration.
+
+<dt><a href="http://www.exalead.com">Exalead</a>
+<dd>A search and navigation platform, including search engine, XML
+ processing libraries, and statistical linguistics.
</dl>
@@ -90,14 +120,4 @@
<dd>Special purpose software for investigating marine vessel hydrodynamics.
-<dt><a href="http://www.flightgear.org">FlightGear</a>
-<dd>An open-source, multi-platform, cooperative flight simulator.
-
-<dt><a href="http://www.simgear.org">SimGear</a>
-<dd>Building-block libraries for quickly assembling 3d simulations, games, and
- visualization applications.
-
-<dt><a href="http://www.aspect-sdm.org">ASPECT</a>
-<dd>A data stream monitoring and visualization tool, for simulation analysis.
-
<dt><a href="http://teem.sf.net">Teem</a>
<dd>A collection of C libraries for manipulating and visualizing
@@ -108,5 +128,18 @@
</dl>
-<h3>Programming</h3>
+<h3>Simulation</h3>
+<dl>
+<dt><a href="http://www.aspect-sdm.org">ASPECT</a>
+<dd>A data stream monitoring and visualization tool, for simulation analysis.
+
+<dt><a href="http://www.flightgear.org">FlightGear</a>
+<dd>An open source, multi-platform, cooperative flight simulator.
+
+<dt><a href="http://www.simgear.org">SimGear</a>
+<dd>Building-block libraries for quickly assembling 3d simulations, games, and
+ visualization applications.
+</dl>
+
+<h3>Compilers and Interpreters</h3>
<dl>
<dt><a href="http://www.perl.org">Perl</a>
@@ -119,14 +152,11 @@
<dd>A dynamic programming language with powerful built-in data types allowing
simple and fast data manipulation.
+</dl>
+<h3>Programming Tools</h3>
+<dl>
<dt><a href="http://www.gnu.org/software/ddd/">GNU ddd</a>
<dd>A graphical front-end for GDB, DBX, WDB, Ladebug, JDB, XDB, bashdb,
- and the Perl, Python and PHP debuggers.
-
-<dt><a href="http://www.trolltech.com/products/qt/">Qt by Trolltech</a>
-<dd>A multi-platform, C++ application development framework.
-
-<dt><a href="http://xmlsoft.org/">libxml2/libxslt</a>
-<dd>GNOME's multi-platform XML C parser and toolkit.
+ and the Perl, Python and PHP debuggers.
<dt><a href="http://oprofile.sf.net">OProfile</a>
@@ -195,8 +225,4 @@
for virtual reality applications.
-<dt><a href="http://www.exalead.com">Exalead</a>
-<dd>A search and navigation platform, including search engine, XML
- processing libraries, and statistical linguistics.
-
<dt><a href="http://www.xmlBlaster.org">xmlBlaster</a>
<dd>A publish/subscribe and PtP message oriented middleware with easy
@@ -206,22 +232,7 @@
<dd>A graphical user environment for PDAs and other Linux devices.
-<dt><a href="http://pan.rebelbase.com">Pan</a>
-<dd>A newsreader supporting offline newsreading, article filtering, and
- multiple connections.
-
-<dt><a href="http://pan.rebelbase.com">Pan</a>
-<dd>A newsreader supporting offline newsreading, article filtering, and
- multiple connections.
-
-<dt><a href="http://www.lysator.liu.se/~alla/dia/">Dia</a>
-<dd>Diagram creator, particularly suited to drawing simple circuit diagrams,
- and more.
-
<dt><a href="http://www.gtk-papaya.org">Papaya</a>
<dd>A GTK+-2.0 MUD client for UNIX and Windows.
-<dt><a href="http://www.pldaniels.com/ripmime">ripMIME</a>
-<dd>Email decoding engine and library.
-
<dt><a href="http://synce.sf.net">SynCE</a>
<dd>WinCE communications layer.
|
|
From: Nicholas N. <nj...@ca...> - 2004-01-31 05:53:24
|
CVS commit by nethercote: Added ST200 VLIW C compiler, fixed a typo. M +1 -1 docs.html 1.7 M +3 -0 users.html 1.21 --- devel-home/valgrind/docs.html #1.6:1.7 @@ -14,5 +14,5 @@ <li><a href="http://www.linux-mag.com/2003-05/compile_03.html">Debugging Memory Problems</a>, by Steve Best. -<li><a href= http://www.tldp.org/HOWTO/Valgrind-HOWTO/">Valgrind HOWTO</a>, by +<li><a href="http://www.tldp.org/HOWTO/Valgrind-HOWTO/">Valgrind HOWTO</a>, by Deepak P. and Sandeep S. </ul> --- devel-home/valgrind/users.html #1.20:1.21 @@ -155,4 +155,7 @@ <dd>A dynamic programming language with powerful built-in data types allowing simple and fast data manipulation. + +<dt><a href="http://www.st.com">ST200 VLIW C compiler</a> +<dd>The STMicroelectronics ST200 VLIW production C compiler. </dl> |
|
From: Nicholas N. <nj...@ca...> - 2004-01-31 05:40:45
|
Hi, I just stumbled across a paper: "Randomized instruction set emulation to disrupt binary code injection attacks" Which you can find here: www.cs.unm.edu/%7Egbarrant/RISE.html as well as an introductory description, and a tarball of their tool, which I haven't tried yet. It seems they modified Valgrind to do some kind of security checking against malicious code injection. Weird. N |
|
From: Nicholas N. <nj...@ca...> - 2004-01-31 05:18:52
|
CVS commit by nethercote:
Added FFEP, Squish, Kdenlive
M +10 -0 users.html 1.22
--- devel-home/valgrind/users.html #1.21:1.22
@@ -127,4 +127,8 @@
structured scientific data.
+<dt><a href="http://www.uni-essen.de/ingmath/ffep/">Free Finite Element
+ Package</a>
+<dd>Numerical libraries for linear finite elements in two dimensions.
+
<dt><a href="http://www.harmonyware.com">HarmonyWare</a>
<dd>NURBS-based geometry translator tools.
@@ -177,4 +181,7 @@
<dt><a href="http://eboxy.sf.net">eboxy</a>
<dd>A tool for creating graphical user interfaces for set-top boxes.
+
+<dt><a href="http://www.froglogic.com/squish/">Squish</a>
+<dd>A cross-platform automated GUI testing framework for Qt/C++ applications.
</dl>
@@ -196,4 +203,7 @@
<dd>A home entertainment media system, complete with servers, clients, and
protocols, handling any TV-presentable content.
+
+<dt><a href="http://www.uchian.pwp.blueyonder.co.uk/kdenlive.html">Kdenlive</a>
+<dd>Video editing suite.
</dl>
|
|
From: Nicholas N. <nj...@ca...> - 2004-01-31 04:41:49
|
CVS commit by nethercote:
Added Dia
M +8 -0 users.html 1.14
--- devel-home/valgrind/users.html #1.13:1.14
@@ -210,4 +210,12 @@
multiple connections.
+<dt><a href="http://pan.rebelbase.com">Pan</a>
+<dd>A newsreader supporting offline newsreading, article filtering, and
+ multiple connections.
+
+<dt><a href="http://www.lysator.liu.se/~alla/dia/">Dia</a>
+<dd>Diagram creator, particularly suited to drawing simple circuit diagrams,
+ and more.
+
<dt><a href="http://www.gtk-papaya.org">Papaya</a>
<dd>A GTK+-2.0 MUD client for UNIX and Windows.
|
|
From: Nicholas N. <nj...@ca...> - 2004-01-31 04:34:54
|
CVS commit by nethercote: Added Samba M +4 -0 users.html 1.17 --- devel-home/valgrind/users.html #1.16:1.17 @@ -194,4 +194,8 @@ <h3>System</h3> <dl> +<dt><a href="http://www.samba.org">Samba</a> +<dd>An open source suite providing seamless file and print services to + SMB/CIFS clients. + <dt><a href="http://www.xinetd.org">Xinetd</a> <dd>A secure and powerful replacement for inetd, the internet services daemon. |
|
From: Nicholas N. <nj...@ca...> - 2004-01-31 03:57:30
|
Hi,
Our FAQ file could do with some rearrangement in the CVS HEAD. I propose
splitting it into sections, and removing some of the questions that no
longer apply.
Here's my suggestion for the sections, and which questions should go in
each one.
1. Trivia: origins of the name 'Valgrind', pronunciation
2. Compiling, installing and configuring: 16
3. Valgrind aborts unexpectedly: 1, 3, (4), 8, (9), (11), (12), 13
4. Unexpected output and behaviour: (5), 6, (7), (10), 14, 15, mention
lack of stack/static checking
5. misc: 17
The numbers in parentheses are the ones I think can be removed, as they
have been addressed in the CVS HEAD.
An extra possibility would be to use the script glibc uses for producing
its FAQ, which pulls out the section names and questions into a nice table
at the top, which makes it easier to find questions. It also
automatically numbers the questions in order, which is nice but means the
numbers can change over time... I think I'd prefer to just remove old
questions and have gaps in the numbering.
N
|
|
From: Nicholas N. <nj...@ca...> - 2004-01-31 02:33:18
|
CVS commit by nethercote:
Various minor tweaks. I'll stop fiddling soon, I promise.
M +0 -3 cvs.html 1.4
M +1 -1 overview.html 1.10
M +9 -8 users.html 1.18
--- devel-home/valgrind/cvs.html #1.3:1.4
@@ -13,7 +13,4 @@
browse the source</a>.
<p>
-Note that our CVS repository is now hosted at KDE rather than
-SourceForge. We switched because SourceForge was too slow and
-unreliable.
<?php
--- devel-home/valgrind/overview.html #1.9:1.10
@@ -52,5 +52,5 @@
programmers. Here are some well-known programs Valgrind can run:
most of KDE and Gnome, Mozilla, OpenOffice, MySQL, Opera,
- KOffice-1.2beta1, emacs-21.2, xemacs-21.5(--pdump), Netscape-4.78,
+ KOffice, emacs-21.2, xemacs-21.5(--pdump), Netscape-4.78,
GCC, AbiWord, etc, etc.
<p>
--- devel-home/valgrind/users.html #1.17:1.18
@@ -9,5 +9,5 @@
<h3>Desktop</h3>
<dl>
-<dt><a href="http://openoffice.org">OpenOffice.org</a>
+<dt><a href="http://openoffice.org">OpenOffice</a>
<dd>A multi-platform office productivity suite.
(<a href="http://www.kegel.com/openoffice/valgrindingOOo.html">Examples</a>
@@ -15,5 +15,5 @@
<dt><a href="http://www.lysator.liu.se/~alla/dia/">Dia</a>
-<dd>Diagram creator, particularly suited to drawing simple circuit diagrams,
+<dd>A diagram creator, particularly suited to drawing simple circuit diagrams,
and more.
</dl>
@@ -22,8 +22,8 @@
<dl>
<dt><a href="http://www.kde.org">KDE</a>
-<dd>Open Source graphical desktop environment for Unix workstations.
+<dd>An open source graphical desktop environment for Unix workstations.
<dt><a href="http://www.koffice.org">KOffice</a>
-<dd>Multi-application, integrated office suite.
+<dd>A multi-application, integrated office suite.
<dt><a href="http://www.konqueror.org">Konqueror</a>
@@ -72,5 +72,5 @@
<dt><a href="http://www.pldaniels.com/ripmime">ripMIME</a>
-<dd>Email decoding engine and library.
+<dd>An email decoding engine and library.
<dt><a href="http://bidwatcher.sf.net">Bidwatcher</a>
@@ -97,5 +97,5 @@
<dt><a href="http://www.teracruz.com/products/dbappliance.aspx">Teracruz
dbAppliance</a>
-<dd>Database performance monitoring and acceleration.
+<dd>A database performance monitoring and acceleration tool.
<dt><a href="http://www.exalead.com">Exalead</a>
@@ -188,5 +188,5 @@
<dt><a href="http://www.aido.org">AIDO</a>
-<dd>Home entertainment media system, complete with servers, clients, and
+<dd>A home entertainment media system, complete with servers, clients, and
protocols, handling any TV-presentable content.
</dl>
@@ -240,5 +240,5 @@
<dt><a href="http://synce.sf.net">SynCE</a>
-<dd>WinCE communications layer.
+<dd>A WinCE communications layer.
</dl>
@@ -246,4 +246,5 @@
Please contact Nick Nethercote (njn25 at cam dot ac dot uk) if you are happy to
have your project added to this list.
+<p>
<?php
|
|
From: Nicholas N. <nj...@ca...> - 2004-01-31 01:42:07
|
CVS commit by nethercote: Added Konqueror, Pan. M +14 -6 users.html 1.11 --- devel-home/valgrind/users.html #1.10:1.11 @@ -5,5 +5,6 @@ ?> -The following projects use or have used Valgrind: +The following projects use or have used Valgrind. + <h3>Desktop</h3> <dl> @@ -16,10 +17,13 @@ <dd>Open Source graphical desktop environment for Unix workstations. -<dt><a href="http://www.gnome.org">GNOME</a> -<dd>A desktop environment and developer platform for Unix and Linux systems. - <dt><a href="http://www.koffice.org">KOffice</a> <dd>Multi-application, integrated office suite. +<dt><a href="http://www.konqueror.org">Konqueror</a> +<dd>A web browser, file manager, and universal document viewing application. + +<dt><a href="http://www.gnome.org">GNOME</a> +<dd>A desktop environment and developer platform for Unix and Linux systems. + <dt><a href="http://www.gnumeric.org">Gnumeric</a> <dd>A replacement for proprietary spreadsheets. @@ -158,5 +162,5 @@ <dl> <dt><a href="http://www.xinetd.org">Xinetd</a> -<dd>A secure and powerful replacement for inetd. +<dd>A secure and powerful replacement for inetd, the internet services daemon. </dl> @@ -194,5 +198,9 @@ <dt><a href="http://opie.handhelds.org">Opie</a> -<dd>A graphical user environment for PDA's and other Linux devices. +<dd>A graphical user environment for PDAs and other Linux devices. + +<dt><a href="http://pan.rebelbase.com">Pan</a> +<dd>A newsreader supporting offline newsreading, article filtering, and + multiple connections. <dt><a href="http://www.gtk-papaya.org">Papaya</a> |
|
From: Nicholas N. <nj...@ca...> - 2004-01-31 01:26:43
|
CVS commit by nethercote: Added awards and articles pages. Both don't have much, but it's a start. Put them in the new 'proselytism' section of the menu; moved the users page there too. A articles.html 1.1 A awards.html 1.1 M +10 -5 menu.inc 1.11 --- devel-home/valgrind/menu.inc #1.10:1.11 @@ -1,3 +1,4 @@ -<!-- Minor hack: " " ensures two-word options stay on a single line --> +<!-- Minor hacks: " " used to ensure two-word options stay on a single + line, and also so that there's a blank line between sections. --> <dl> <dt><b>About</b> @@ -5,12 +6,11 @@ <dt><a href="overview.html"> Overview</a> <dt><a href="tools.html"> Tools</a> -<dt><a href="users.html"> Users</a> <dt><a href="related.html"> Related Projects</a> -<p> +<dt> <dt><b>Code</b> <dt><a href="sysreqs.html"> System Requirements</a> <dt><a href="downloads.html">Downloads</a> <dt><a href="cvs.html"> CVS Repository</a> -<p> +<dt> <dt><b>Support</b> <dt><a href="docs.html"> Documentation</a> @@ -19,5 +19,10 @@ <dt><a href="bugs.html"> Bug Reports</a> <dt><a href="features.html"> Feature Requests</a> -<p> +<dt> +<dt><b>Proselytism</b> +<dt><a href="users.html"> Users</a> +<dt><a href="articles.html"> Articles</a> +<dt><a href="awards.html"> Awards</a> +<dt> <dt><b>Feedback</b> <dt><a href="surveys.html"> Surveys</a> |
|
From: Nicholas N. <nj...@ca...> - 2004-01-31 01:24:17
|
CVS commit by nethercote: Added StarOffice M +4 -1 users.html 1.19 --- devel-home/valgrind/users.html #1.18:1.19 @@ -10,8 +10,11 @@ <dl> <dt><a href="http://openoffice.org">OpenOffice</a> -<dd>A multi-platform office productivity suite. +<dd>An open source multi-platform office productivity suite. (<a href="http://www.kegel.com/openoffice/valgrindingOOo.html">Examples</a> of bugs found.) +<dt><a href="http://wwws.sun.com/software/star/staroffice/index.html">StarOffice</a> +<dd>A commercial multi-platform office productivity suite, based on OpenOffice. + <dt><a href="http://www.lysator.liu.se/~alla/dia/">Dia</a> <dd>A diagram creator, particularly suited to drawing simple circuit diagrams, |
|
From: Nicholas N. <nj...@ca...> - 2004-01-31 00:12:02
|
CVS commit by nethercote: Renaming "Related Tools" --> "Related Projects" to avoid confusion with our specific use of the word "tool". M +1 -1 menu.inc 1.10 M +3 -3 related.html 1.6 --- devel-home/valgrind/menu.inc #1.9:1.10 @@ -6,5 +6,5 @@ <dt><a href="tools.html"> Tools</a> <dt><a href="users.html"> Users</a> -<dt><a href="related.html"> Related Tools</a> +<dt><a href="related.html"> Related Projects</a> <p> <dt><b>Code</b> --- devel-home/valgrind/related.html #1.5:1.6 @@ -1,5 +1,5 @@ <?php - $page_title = "Related Tools"; - $page_heading = "Related Tools"; + $page_title = "Related Projects"; + $page_heading = "Related Projects"; include "header.inc" ?> @@ -40,5 +40,5 @@ <h3>Graphical Front-Ends</h3> -Several graphical front-ends have been built for Valgrind tools. These +Several graphical front-ends have been built for Valgrind. These are the ones we know about. |
|
From: Nicholas N. <nj...@ca...> - 2004-01-31 00:07:28
|
CVS commit by nethercote: Fix PHP url M +1 -1 users.html 1.16 --- devel-home/valgrind/users.html #1.15:1.16 @@ -146,5 +146,5 @@ <dd>A general-purpose programming language; the duct-tape of the internet. -<dt><a href="http://www.php.org">PHP</a> +<dt><a href="http://www.php.net">PHP</a> <dd>A web-oriented scripting language. |