|Information Source Code Documentation Contact How to Help Gallery|
Valgrind Survey, November 2003
Table of Contents
The survey was sent to vg-users list, plus 226 people who had contacted me directly in the past 18 months (10 of those bounced).
We received 116 full responses (plus 2 or 3 that gave no useful info). 115 were in English. 1 was in French. Fortunately the French was pretty easy.
Nationalities of the 226 people directly contacted (based on email suffixes; lots of .com ones so some countries might be missed):
The survey wasn't well structured -- too verbose, not quantitative enough. I had to interpret written answers to fit them into categories a lot. Collating it all was cumbersome, and I probably made mistakes transcribing lots of things. But the results should hopefully be representative.
Generally, when I say "Valgrind" it usually refers to Memcheck, although judge each mention by the context. It should be obvious when I'm referring to other skins.
I've come up with an improved version that could be used in the future, or hung off the web page.
- huge range of software types, almost everything imagineable - very roughly, number of language mentions: 45% C, 40% C++, 15% other - projects ranging from 1 programmer to 10s, even 100s - project sizes ranging from tiny to 25 MLOC
- Memcheck dominates massively; partly because it's the most useful, but confusion about skins means its default-ness is a huge advantage. - Addrcheck is holding its weight in the distro - Calltree is doing very well outside the distro, probably should replace Cachegrind - Cachegrind and Helgrind aren't holding their weight in the distro.
Use of Valgrind:
- vast majority (90%?) run it manually, a few use it as part of automated testing - most commonly used when a bug is found or suspected (40% of repondents) - also commonly before releases, and when big changes are made
- lots of people have used Purify, Valgrind compares well - Valgrind's pros: no recompilation, free, no horrible license server - Purify's pros: GUI is nicer, and allows some interactivity - Equal points: technically seem similar, eg. speed, bugs found - Valgrind compares well with insure/insure++ - Valgrind thrashes other error-checking tools - KCachegrind seems to compare pretty well with other profilers
Good things about the software:
- praise about bug-finding:  - lack of recompilation:  - free software/Linux-ness:  - praise for error messages: 
Bad things/improvements for the software:
- no complaints:  - slowness:  - robustness problems:  - docs bad:  - desired features - GUI:  - static binaries:  - interactive leak checking:  - stack variable checking: [ ] - annoying features - error messages:  - external skins hard to use: [ 6] - suppressions difficult: [ 5]
Good things about non-software:
- most people generally happy with development:  - development praised:  - mailing list is good: [ 7]
Bad things about non-software:
- webpage is bad, doesn't link to skins/GUIs:  - skins are confusing, poorly understood:  - releases aren't always done well:  - Valgrind not marketed well: [ 6] - a few patches have been handled poorly
Recommendations that we should actively seek donations, etc.
- Windows most popular, although not sure about which version - Solaris next, aroused the most number of passionate responses - FreeBSD the most popular other Unix, just ahead of OS X.
- PowerPC, SPARC and AMD-64 most popular. - IA64 a fair way back.
Copyright © 2000-2013 Valgrind™ Developers