[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-commits
Subject: devel-home/valgrind
From: Nicholas Nethercote <njn25 () cam ! ac ! uk>
Date: 2004-01-31 22:30:18
Message-ID: 20040131223018.528429953 () office ! kde ! org
[Download RAW message or body]
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>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic