1<html> 2<head> 3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> 4<title>1.�AUTHORS</title> 5<link rel="stylesheet" href="vg_basic.css" type="text/css"> 6<meta name="generator" content="DocBook XSL Stylesheets V1.75.2"> 7<link rel="home" href="index.html" title="Valgrind Documentation"> 8<link rel="up" href="dist.html" title="Valgrind Distribution Documents"> 9<link rel="prev" href="dist.html" title="Valgrind Distribution Documents"> 10<link rel="next" href="dist.news.html" title="2.�NEWS"> 11</head> 12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"> 13<div><table class="nav" width="100%" cellspacing="3" cellpadding="3" border="0" summary="Navigation header"><tr> 14<td width="22px" align="center" valign="middle"><a accesskey="p" href="dist.html"><img src="images/prev.png" width="18" height="21" border="0" alt="Prev"></a></td> 15<td width="25px" align="center" valign="middle"><a accesskey="u" href="dist.html"><img src="images/up.png" width="21" height="18" border="0" alt="Up"></a></td> 16<td width="31px" align="center" valign="middle"><a accesskey="h" href="index.html"><img src="images/home.png" width="27" height="20" border="0" alt="Up"></a></td> 17<th align="center" valign="middle">Valgrind Distribution Documents</th> 18<td width="22px" align="center" valign="middle"><a accesskey="n" href="dist.news.html"><img src="images/next.png" width="18" height="21" border="0" alt="Next"></a></td> 19</tr></table></div> 20<div class="chapter" title="1.�AUTHORS"> 21<div class="titlepage"><div><div><h2 class="title"> 22<a name="dist.authors"></a>1.�AUTHORS</h2></div></div></div> 23<div class="literallayout"><p><br> 24��������<br> 25Julian�Seward�was�the�original�founder,�designer�and�author�of<br> 26Valgrind,�created�the�dynamic�translation�frameworks,�wrote�Memcheck,<br> 27the�3.X�versions�of�Helgrind,�Ptrcheck,�DHAT,�and�did�lots�of�other<br> 28things.<br> 29<br> 30Nicholas�Nethercote�did�the�core/tool�generalisation,�wrote<br> 31Cachegrind�and�Massif,�and�tons�of�other�stuff.<br> 32<br> 33Tom�Hughes�did�a�vast�number�of�bug�fixes,�helped�out�with�support�for<br> 34more�recent�Linux/glibc�versions,�set�up�the�present�build�system,�and�has<br> 35helped�out�with�test�and�build�machines.<br> 36<br> 37Jeremy�Fitzhardinge�wrote�Helgrind�(in�the�2.X�line)�and�totally<br> 38overhauled�low-level�syscall/signal�and�address�space�layout�stuff,<br> 39among�many�other�things.<br> 40<br> 41Josef�Weidendorfer�wrote�and�maintains�Callgrind�and�the�associated<br> 42KCachegrind�GUI.<br> 43<br> 44Paul�Mackerras�did�a�lot�of�the�initial�per-architecture�factoring<br> 45that�forms�the�basis�of�the�3.0�line�and�was�also�seen�in�2.4.0.<br> 46He�also�did�UCode-based�dynamic�translation�support�for�PowerPC,�and<br> 47created�a�set�of�ppc-linux�derivatives�of�the�2.X�release�line.<br> 48<br> 49Greg�Parker�wrote�the�Mac�OS�X�port.<br> 50<br> 51Dirk�Mueller�contributed�the�malloc/free�mismatch�checking<br> 52and�other�bits�and�pieces,�and�acts�as�our�KDE�liaison.<br> 53<br> 54Robert�Walsh�added�file�descriptor�leakage�checking,�new�library<br> 55interception�machinery,�support�for�client�allocation�pools,�and�minor<br> 56other�tweakage.<br> 57<br> 58Bart�Van�Assche�wrote�and�maintains�DRD.<br> 59<br> 60Cerion�Armour-Brown�worked�on�PowerPC�instruction�set�support�in�the<br> 61Vex�dynamic-translation�framework.��Maynard�Johnson�improved�the<br> 62Power6�support.<br> 63<br> 64Kirill�Batuzov�and�Dmitry�Zhurikhin�did�the�NEON�instruction�set<br> 65support�for�ARM.��Donna�Robinson�did�the�v6�media�instruction�support.<br> 66<br> 67Donna�Robinson�created�and�maintains�the�very�excellent<br> 68http://www.valgrind.org.<br> 69<br> 70Vince�Weaver�wrote�and�maintains�BBV.<br> 71<br> 72Frederic�Gobry�helped�with�autoconf�and�automake.<br> 73<br> 74Daniel�Berlin�modified�readelf's�dwarf2�source�line�reader,�written�by�Nick<br> 75Clifton,�for�use�in�Valgrind.o<br> 76<br> 77Michael�Matz�and�Simon�Hausmann�modified�the�GNU�binutils�demangler(s)�for<br> 78use�in�Valgrind.<br> 79<br> 80David�Woodhouse�has�helped�out�with�test�and�build�machines�over�the�course<br> 81of�many�releases.<br> 82<br> 83Many,�many�people�sent�bug�reports,�patches,�and�helpful�feedback.<br> 84<br> 85Development�of�Valgrind�was�supported�in�part�by�the�Tri-Lab�Partners<br> 86(Lawrence�Livermore�National�Laboratory,�Los�Alamos�National<br> 87Laboratory,�and�Sandia�National�Laboratories)�of�the�U.S.�Department<br> 88of�Energy's�Advanced�Simulation�&�Computing�(ASC)�Program.<br> 89<br> 90����</p></div> 91</div> 92<div> 93<br><table class="nav" width="100%" cellspacing="3" cellpadding="2" border="0" summary="Navigation footer"> 94<tr> 95<td rowspan="2" width="40%" align="left"> 96<a accesskey="p" href="dist.html"><<�Valgrind Distribution Documents</a>�</td> 97<td width="20%" align="center"><a accesskey="u" href="dist.html">Up</a></td> 98<td rowspan="2" width="40%" align="right">�<a accesskey="n" href="dist.news.html">2.�NEWS�>></a> 99</td> 100</tr> 101<tr><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td></tr> 102</table> 103</div> 104</body> 105</html> 106
