Halaman utama Jelajahi Bantuan
Masuk
trn
/
duma
cermin dari https://github.com/johnsonjh/duma.git
Liatin 1
Bintangi 1
Fork 0
Berkas
Cabang: master
Ranting Tag
duma
/
Attic
/
comparisons
/
memCheckers.html

memCheckers.html 16 KB
Permalink Riwayat Mentahan

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367 
  1. <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
    2. 

  2. <html><head><title>Comparison of Free Memory Checkers</title>
    3. 

  3. 

  4. <link rel="start" type="text/html" href="http://www.cs.utexas.edu/%7Ejpmartin/index.html">
    5. 

  5. <link rel="up" type="text/html" href="http://www.cs.utexas.edu/%7Ejpmartin/resources.html">
    6. 

  6. <link rel="icon" type="image/png" href="http://www.cs.utexas.edu/%7Ejpmartin/longhorn_icon.png">
    7. 

  7. 

  8. 

  9. <link rel="styleSheet" href="memCheckers-Dateien/jpstyle.css" title="default stylesheet">
    10. 

  10. <link rel="Alternate StyleSheet" href="memCheckers-Dateien/boringstyle.css" title="alternate
    11. 

  11. (old-fashioned) stylesheet"></head><body>
    12. 

  12. 

  13. <h1><a class="title" href="http://www.cs.utexas.edu/%7Ejpmartin/index.html">Jean-Philippe Martin</a> |
    14. 

  14. <a class="title" href="http://www.cs.utexas.edu/%7Ejpmartin/resources.html">Resources</a> | Memory Checkers Comparison </h1>
    15. 

  15. <hr>
    16. 

  16. <p>
    17. 

  17. 

  18. </p><h3>Memory Checkers</h3>
    19. 

  19. 

  20. Memory checkers are debugging tools that help programmers find
    21. 

  21. improper use of pointers, typically memory leaks.
    22. 

  22. 

  23. <p align="justify">
    24. 

  24. There are some freely available memory checkers. I ran a series of
    25. 

  25. very simple tests to determine what they can do. The <b>wrong</b>
    26. 

  26. series of tests contains code that makes pointer mistakes that are not
    27. 

  27. memory leaks, for example freeing a pointer twice, writing to
    28. 

  28. uninitialized memory or using delete instead of delete []. The
    29. 

  29. <b>leak</b> series of tests contains simple memory leaks,
    30. 

  30. i.e. pointers that are allocated but not released. The <b>ok</b>
    31. 

  31. series of tests contains programs that are correct and thus should not
    32. 

  32. cause the memory checker to output any alarm message.
    33. 

  33. </p>
    34. 

  34. 

  35. <h3>C tests</h3>
    36. 

  36. 

  37. (updated 3/10/2006)<p>
    38. 

  38. 

  39. <table border="1">
    40. 

  40.   <colgroup>
    41. 

  41.   </colgroup><colgroup span="3">
    42. 

  42.   </colgroup><colgroup span="2">
    43. 

  43.   </colgroup><colgroup>
    44. 

  44. 

  45. </colgroup><tbody><tr>
    46. 

  46.   <th>Checker
    47. 

  47. 

  48.   </th><th><a class="title" href="http://www.cs.utexas.edu/%7Ejpmartin/memcheck/wrong1.c">wrong1.c</a>
    49. 

  49.   </th><th><a class="title" href="http://www.cs.utexas.edu/%7Ejpmartin/memcheck/wrong3.c">wrong3.c</a>
    50. 

  50.   </th><th><a class="title" href="http://www.cs.utexas.edu/%7Ejpmartin/memcheck/wrong6.c">wrong6.c</a>
    51. 

  51.   </th><th><a class="title" href="http://www.cs.utexas.edu/%7Ejpmartin/memcheck/wrong7.c">wrong7.c</a>
    52. 

  52.   </th><th><a class="title" href="http://www.cs.utexas.edu/%7Ejpmartin/memcheck/leak1.c">leak1.c</a>
    53. 

  53.   </th><th><a class="title" href="http://www.cs.utexas.edu/%7Ejpmartin/memcheck/leak2.c">leak2.c</a>
    54. 

  54.   </th><th><a class="title" href="http://www.cs.utexas.edu/%7Ejpmartin/memcheck/ok5.c">ok5.c </a>
    55. 

  55. 

  56. </th></tr>
    57. 

  57. 

  58. 

  59. 

  60. <tr align="center">
    61. 

  61.   <td><a class="title" href="http://www.gnu.org/manual/glibc-2.2.5/html_node/Heap-Consistency-Checking.html">MALLOC_CHECK_</a>
    62. 

  62. 

  63.   </td><td><b><font color="darkgreen">OK</font></b>
    64. 

  64.   </td><td><b><font color="darkred">missed</font></b>
    65. 

  65.   </td><td><b><font color="darkred">missed</font></b>
    66. 

  66.  </td><td><b><font color="darkgreen">OK</font></b><a href="http://www.cs.utexas.edu/%7Ejpmartin/memcheck/wrong7.out">*</a>
    67. 

  67.   </td><td><b><font color="darkred">missed</font></b>
    68. 

  68.   </td><td><b><font color="darkred">missed</font></b>
    69. 

  69.   </td><td><b><font color="darkgreen">OK</font></b>
    70. 

  70. </td></tr>
    71. 

  71. 

  72. <tr align="center">
    73. 

  73.   <td><a class="title" href="http://dmalloc.com/">dmalloc</a>
    74. 

  74.   </td><td><b><font color="darkgreen">OK</font></b>
    75. 

  75.   </td><td><b><font color="darkred">missed</font></b> 
    76. 

  76.   </td><td><b><font color="darkred">missed</font></b> 
    77. 

  77.   </td><td><b><font color="darkgreen">OK</font></b>
    78. 

  78.   </td><td><b><font color="darkgreen">OK</font></b>
    79. 

  79.   </td><td><b><font color="darkgreen">OK</font></b>
    80. 

  80.   </td><td><b><font color="darkgreen">OK</font></b>
    81. 

  81. </td></tr>
    82. 

  82. 

  83. <tr align="center">
    84. 

  84.   <td><a class="title" href="http://prj.softpixel.com/mcd/">memCheckDeluxe</a>
    85. 

  85. 

  86.   </td><td><b><font color="darkred">missed</font></b>
    87. 

  87.   </td><td><b><font color="darkred">missed</font></b>
    88. 

  88.   </td><td><b><font color="darkred">missed</font></b>
    89. 

  89.   </td><td><b><font color="darkred">missed</font></b>
    90. 

  90.   </td><td><b><font color="darkgreen">OK</font></b>
    91. 

  91.   </td><td><b><font color="darkgreen">OK</font></b>
    92. 

  92.   </td><td><b><font color="darkgreen">OK</font></b>
    93. 

  93. </td></tr>
    94. 

  94. 

  95. <tr align="center">
    96. 

  96.   <td><a class="title" href="http://www.linkdata.se/sourcecode.html">memwatch</a>
    97. 

  97. 

  98.   </td><td><b><font color="darkgreen">OK</font></b>
    99. 

  99.   </td><td><b><font color="darkred">missed</font></b>
    100. 

  100.   </td><td><b><font color="darkred">missed</font></b><a href="http://www.cs.utexas.edu/%7Ejpmartin/memcheck/memwatch-response.txt">*</a>
    101. 

  101.  </td><td><b><font color="darkgreen">OK</font></b>
    102. 

  102.   </td><td><b><font color="darkgreen">OK</font></b>
    103. 

  103.   </td><td><b><font color="darkgreen">OK</font></b>
    104. 

  104.   </td><td><b><font color="darkgreen">OK</font></b>
    105. 

  105. </td></tr>
    106. 

  106. 

  107. <tr align="center">
    108. 

  108.   <td><a class="title" href="http://duma.sourceforge.net/">DUMA</a>
    109. 

  109.   </td><td><b><font color="darkgreen">OK</font></b>
    110. 

  110. <!-- segfaults on the bad write, but misses the bad read -->
    111. 

  111.   </td><td><b><font color="darkred">missed</font></b> 
    112. 

  112.   </td><td><b><font color="darkred">missed</font></b> 
    113. 

  113. <!-- segfaults on the first bug. That counts as finding it -->
    114. 

  114.   </td><td><b><font color="darkgreen">OK</font></b>
    115. 

  115.   </td><td><b><font color="darkgreen">OK</font></b>
    116. 

  116.   </td><td><b><font color="darkgreen">OK<a href="http://www.cs.utexas.edu/%7Ejpmartin/duma-l2c.txt">*</a></font></b>
    117. 

  117.   </td><td><b><font color="darkgreen">OK</font></b>
    118. 

  118. </td></tr>
    119. 

  119. 

  120. 

  121. 

  122. <tr align="center">
    123. 

  123.   <td><a class="title" href="http://devel-home.kde.org/%7Esewardj/">valgrind</a>
    124. 

  124. 

  125.   </td><td><b><font color="darkgreen">OK</font></b>
    126. 

  126.   </td><td><b><font color="darkgreen">OK</font></b>
    127. 

  127.   </td><td><b><font color="darkred">missed</font></b>
    128. 

  128.  </td><td><b><font color="darkgreen">OK</font></b>
    129. 

  129.   </td><td><b><font color="darkgreen">OK</font></b>
    130. 

  130.   </td><td><b><font color="darkgreen">OK</font></b>
    131. 

  131.   </td><td><b><font color="darkgreen">OK</font></b>
    132. 

  132. </td></tr>
    133. 

  133. 

  134. 

  135. 

  136. </tbody></table>
    137. 

  137. 

  138. </p><p>
    139. 

  139. 

  140. </p><h3>C++ tests</h3>
    141. 

  141. 

  142. <table border="1">
    143. 

  143. <tbody><tr>
    144. 

  144.   <th>Checker
    145. 

  145. 

  146.   </th><th><a class="title" href="http://www.cs.utexas.edu/%7Ejpmartin/memcheck/wrong1.cc">wrong1.cc</a>
    147. 

  147.   </th><th><a class="title" href="http://www.cs.utexas.edu/%7Ejpmartin/memcheck/wrong2.cc">wrong2.cc</a>
    148. 

  148.   </th><th><a class="title" href="http://www.cs.utexas.edu/%7Ejpmartin/memcheck/wrong3.cc">wrong3.cc</a>
    149. 

  149.   </th><th><a class="title" href="http://www.cs.utexas.edu/%7Ejpmartin/memcheck/wrong4.cc">wrong4.cc</a>
    150. 

  150.   </th><th><a class="title" href="http://www.cs.utexas.edu/%7Ejpmartin/memcheck/wrong5.cc">wrong5.cc</a>
    151. 

  151.   </th><th><a class="title" href="http://www.cs.utexas.edu/%7Ejpmartin/memcheck/wrong6.cc">wrong6.cc</a>
    152. 

  152.   </th><th><a class="title" href="http://www.cs.utexas.edu/%7Ejpmartin/memcheck/leak1.cc">leak1.cc</a>
    153. 

  153.   </th><th><a class="title" href="http://www.cs.utexas.edu/%7Ejpmartin/memcheck/leak2.cc">leak2.cc</a>
    154. 

  154.   </th><th><a class="title" href="http://www.cs.utexas.edu/%7Ejpmartin/memcheck/ok5.cc">ok5.cc</a>
    155. 

  155. 

  156. </th></tr>
    157. 

  157. 

  158. 

  159. <tr align="center">
    160. 

  160.   <td><a class="title" href="http://www.gnu.org/manual/glibc-2.2.5/html_node/Heap-Consistency-Checking.html">MALLOC_CHECK_</a>
    161. 

  161. 

  162.   </td><td><b><font color="darkgreen">OK</font></b>
    163. 

  163.   </td><td><b><font color="darkgreen">OK</font></b>
    164. 

  164.   </td><td><b><font color="darkred">missed</font></b>
    165. 

  165.   </td><td><b><font color="darkred">missed</font></b>
    166. 

  166.   </td><td><b><font color="darkgreen">OK</font></b>
    167. 

  167.   </td><td><b><font color="darkred">missed</font></b>
    168. 

  168.   </td><td><b><font color="darkred">missed</font></b>
    169. 

  169.   </td><td><b><font color="darkred">missed</font></b>
    170. 

  170.   </td><td><b><font color="darkgreen">OK</font></b>
    171. 

  171. </td></tr>
    172. 

  172. 

  173. <tr align="center">
    174. 

  174.   <td><a class="title" href="http://dmalloc.com/">dmalloc</a>
    175. 

  175.   </td><td><b><font color="darkgreen">OK</font></b>
    176. 

  176.   </td><td><b><font color="darkgreen">OK</font><a href="http://www.cs.utexas.edu/%7Ejpmartin/memcheck/dmalloc-wrong2.txt">*</a></b>
    177. 

  177.   </td><td><b><font color="darkred">missed</font><a href="http://www.cs.utexas.edu/%7Ejpmartin/memcheck/dmalloc-wrong3.txt">*</a></b>
    178. 

  178.   </td><td><b><font color="darkred">missed</font></b>
    179. 

  179.   </td><td><b><font color="darkgreen">OK</font></b>
    180. 

  180.   </td><td><b><font color="darkred">missed</font></b>
    181. 

  181.   </td><td><b><font color="darkgreen">OK</font></b>
    182. 

  182.   </td><td><b><font color="darkgreen">OK</font></b>
    183. 

  183.   </td><td><b><font color="darkred">missed</font><a href="http://www.cs.utexas.edu/%7Ejpmartin/memcheck/dmalloc-ok5.txt">*</a></b>
    184. 

  184. </td></tr>
    185. 

  185. 

  186. <tr align="center">
    187. 

  187.   <td><a class="title" href="http://duma.sourceforge.net/">DUMA</a>
    188. 

  188.   </td><td><b><font color="darkgreen">OK</font></b>
    189. 

  189.   </td><td><b><font color="darkgreen">OK</font></b>
    190. 

  190. <!-- caught the write to uninitialized memory, but not the read -->
    191. 

  191.   </td><td><b><font color="darkred">missed</font></b>
    192. 

  192.   </td><td><b><font color="darkgreen">OK</font></b>
    193. 

  193.   </td><td><b><font color="darkgreen">OK</font></b>
    194. 

  194.   </td><td><b><font color="darkred">missed</font></b>
    195. 

  195.   </td><td><b><font color="darkgreen">OK</font></b>
    196. 

  196.   </td><td><b><font color="darkgreen">OK</font></b>
    197. 

  197.   </td><td><b><font color="darkred">missed</font></b>
    198. 

  198. </td></tr>
    199. 

  199. 

  200. 

  201. <tr align="center">
    202. 

  202.   <td><a class="title" href="http://devel-home.kde.org/%7Esewardj/">valgrind</a>
    203. 

  203. 

  204.   </td><td><b><font color="darkgreen">OK</font></b>
    205. 

  205.   </td><td><b><font color="darkgreen">OK</font></b>
    206. 

  206.   </td><td><b><font color="darkgreen">OK<a href="http://www.cs.utexas.edu/%7Ejpmartin/valgrind-w3cc.txt">*</a></font></b>
    207. 

  207.   </td><td><b><font color="darkgreen">OK</font></b>
    208. 

  208.   </td><td><b><font color="darkgreen">OK</font></b>
    209. 

  209.   </td><td><b><font color="darkred">missed</font></b>
    210. 

  210.   </td><td><b><font color="darkgreen">OK</font></b>
    211. 

  211.   </td><td><b><font color="darkgreen">OK</font></b>
    212. 

  212.   </td><td><b><font color="darkgreen">OK</font></b>
    213. 

  213. </td></tr>
    214. 

  214. 

  215. </tbody></table>
    216. 

  216. <p>
    217. 

  217. 

  218. </p><h3>Conclusion</h3>
    219. 

  219. 

  220. <p align="justify">
    221. 

  221. memWatch and memCheckDeluxe are both memory leak detectors, and they
    222. 

  222. passed all the memory leak tests. Memwatch wins this round because it
    223. 

  223. was able to detect the double-free in wrong1.c and the out-of-bounds
    224. 

  224. accesses in the dynamically allocated array of wrong7.c (not the
    225. 

  225. static array of wrong6 - but no one else did, either).
    226. 

  226. Both programs are designed to work with C and require a
    227. 

  227. recompilation.
    228. 

  228. </p>
    229. 

  229. 

  230. <p align="justify">
    231. 

  231. MALLOC_CHECK_ is an interesting test: it is triggered simply by
    232. 

  232. setting the environment variable MALLOC_CHECK_ to 1, and the rest of
    233. 

  233. the magic is done by glibc (see the link in references, below). This
    234. 

  234. is the easiest check to set up and it requires no recompilation. It
    235. 

  235. detected the double free in wrong1 and the mismatched malloc/delete or
    236. 

  236. new/free pairs in wrong2.cc and wrong5.cc. It was able to see that
    237. 

  237. something was fishy in wrong7.c, but it reports a single error at the "free"
    238. 

  238. instead of when we are accessing the memory instead of two errors, for
    239. 

  239. each out-of-bounds access. MALLOC_CHECK_ cannot detect
    240. 

  240. memory leaks and did not detect the use of uninitialized memory in
    241. 

  241. wrong3.
    242. 

  242. </p>
    243. 

  243. 

  244. <p align="justify">
    245. 

  245. dmalloc is more than a leak detector, but it didn't detect as
    246. 

  246. many bad cases as valgrind and requires a recompile. Also, its C++
    247. 

  247. support is (in the author's words) minimal. In particular, I have not
    248. 

  248. been able to get dmalloc to report line numbers with C++ (<a href="http://www.cs.utexas.edu/%7Ejpmartin/memcheck/dmalloc-cpp.txt">log</a>), although that feature mostly
    249. 

  249. works with C code - in both leak1.c and leak2.c it pointed to 
    250. 

  250. the <tt>return()</tt> instead of the line that allocated the unfreed
    251. 

  251. memory. Dmalloc also often reports unfreed memory, even for programs
    252. 

  252. that are correct. This may be because of errors in the c++ library,
    253. 

  253. but it makes the reports harder to read. In contrast, valgrind has a
    254. 

  254. way to hide leaks that it knows about so its reports are more
    255. 

  255. clear. See also the <a href="http://www.cs.utexas.edu/%7Ejpmartin/memcheck/dmalloc-feedback.txt">author's comments</a>.
    256. 

  256. </p>
    257. 

  257. 

  258. <p align="justify">
    259. 

  259. valgrind is clearly the winner of this little contest. valgrind
    260. 

  260. requires no recompilation of the program, so it's very easy to set
    261. 

  261. up. It identified almost all of the incorrect pointer uses and memory
    262. 

  262. leaks. The only test that it missed is wrong6, in which we break the
    263. 

  263. bounds of an array. No other checker spotted that one, though. Also,
    264. 

  264. valgrind has been improved since we ran this test, so it may perform
    265. 

  265. even better than what we show here.
    266. 

  266. </p>
    267. 

  267. 

  268. <p align="justify">
    269. 

  269. DUMA is a very close second. The results I am posting here come from
    270. 

  270. Koneru Srikanth (kpsrikanth at gmail dot com) who generously sent them
    271. 

  271. to me. DUMA seems not to require a recompile, but the tests were run
    272. 

  272. on recompiled code. DUMA performs really well. It was also able to
    273. 

  273. detect out-of-bounds writes 
    274. 

  274. (it is reported as failing wrong3.cc because it missed the
    275. 

  275. out-of-bounds read). If for some reason valgrind does not work for
    276. 

  276. you, then I recommend that you give DUMA a spin.
    277. 

  277. 

  278. 

  279. </p><h3>Reference</h3>
    280. 

  280. 

  281. I tested:
    282. 

  282. 

  283. <ul>
    284. 

  284.   <li><a href="http://www.gnu.org/manual/glibc-2.2.5/html_node/Heap-Consistency-Checking.html">MALLOC_CHECK_</a>
    285. 

  285.   for glibc (C and C++: requires no recompilation)
    286. 

  286. </li><li><a href="http://dmalloc.com/">dmalloc-5.2.2</a> (C, minimal C++ support; requires recompilation)
    287. 

  287. </li><li><a href="http://prj.softpixel.com/mcd/">memCheckDeluxe-1.2.2</a> (C,
    288. 

  288. some C++. Requires recompilation)
    289. 

  289. </li><li><a href="http://www.linkdata.se/sourcecode.html">memwatch-2.71</a> (C
    290. 

  290. only; requires recompilation)
    291. 

  291.   </li><li><a href="http://devel-home.kde.org/%7Esewardj/">valgrind-1.9.6</a>
    292. 

  292.   (C, C++ and more: requires no recompilation)
    293. 

  293.   </li><li><a href="http://duma.sourceforge.net/">DUMA</a> version 2.4.26
    294. 

  294.   (C and C++. Documentation says that no recompilation is needed, but
    295. 

  295.   the tests were run on recompiled code) (as mentioned above, these tests
    296. 

  296.   were contributed by Koneru Srikanth).
    297. 

  297. </li></ul>
    298. 

  298. 

  299. I did not test:
    300. 

  300. 

  301. <ul>
    302. 

  302.   <li><a href="http://perens.com/FreeSoftware/">electric fence-2.1</a>
    303. 

  303.   (did not compile on first attempt (<a href="http://www.cs.utexas.edu/%7Ejpmartin/memcheck/efence-output.txt">log</a>))
    304. 

  304.   </li><li><a href="http://check.sourceforge.net/">Checker-0.9.9.1</a> (did
    305. 

  305.   not compile on first attempt (<a href="http://www.cs.utexas.edu/%7Ejpmartin/memcheck/checker-output.txt">log</a>); author suggests I use
    306. 

  306.   valgrind instead)
    307. 

  307. </li></ul>
    308. 

  308. 

  309. Test programs:
    310. 

  310. 

  311. <ul>
    312. 

  312.   <li><a href="http://www.cs.utexas.edu/%7Ejpmartin/memcheck/wrong1.c">wrong1.c</a>
    313. 

  313.   </li><li><a href="http://www.cs.utexas.edu/%7Ejpmartin/memcheck/wrong3.c">wrong3.c</a>
    314. 

  314.   </li><li><a href="http://www.cs.utexas.edu/%7Ejpmartin/memcheck/wrong6.c">wrong6.c</a>
    315. 

  315.   </li><li><a href="http://www.cs.utexas.edu/%7Ejpmartin/memcheck/wrong7.c">wrong7.c</a>
    316. 

  316.   </li><li><a href="http://www.cs.utexas.edu/%7Ejpmartin/memcheck/leak1.c">leak1.c</a>
    317. 

  317.   </li><li><a href="http://www.cs.utexas.edu/%7Ejpmartin/memcheck/leak2.c">leak2.c</a>
    318. 

  318.   </li><li><a href="http://www.cs.utexas.edu/%7Ejpmartin/memcheck/ok5.c">ok5.c </a>
    319. 

  319. 

  320.   </li><li><a href="http://www.cs.utexas.edu/%7Ejpmartin/memcheck/wrong1.cc">wrong1.cc</a>
    321. 

  321.   </li><li><a href="http://www.cs.utexas.edu/%7Ejpmartin/memcheck/wrong2.cc">wrong2.cc</a>
    322. 

  322.   </li><li><a href="http://www.cs.utexas.edu/%7Ejpmartin/memcheck/wrong3.cc">wrong3.cc</a>
    323. 

  323.   </li><li><a href="http://www.cs.utexas.edu/%7Ejpmartin/memcheck/wrong4.cc">wrong4.cc</a>
    324. 

  324.   </li><li><a href="http://www.cs.utexas.edu/%7Ejpmartin/memcheck/wrong5.cc">wrong5.cc</a>
    325. 

  325.   </li><li><a href="http://www.cs.utexas.edu/%7Ejpmartin/memcheck/wrong6.cc">wrong6.cc</a>
    326. 

  326.   </li><li><a href="http://www.cs.utexas.edu/%7Ejpmartin/memcheck/leak1.cc">leak1.cc</a>
    327. 

  327.   </li><li><a href="http://www.cs.utexas.edu/%7Ejpmartin/memcheck/leak2.cc">leak2.cc</a>
    328. 

  328.   </li><li><a href="http://www.cs.utexas.edu/%7Ejpmartin/memcheck/ok5.cc">ok5.cc</a>
    329. 

  329. 

  330. </li></ul>
    331. 

  331. 

  332. <h3>ToDo</h3>
    333. 

  333. 

  334. The following memory checkers have been mentionned to me but I haven't
    335. 

  335. tried them yet:
    336. 

  336. <ul>
    337. 

  337. <li>mpatrol at http://www.cbmamiga.demon.co.uk/mpatrol/
    338. 

  338. </li></ul>
    339. 

  339. 

  340. <h3>Change History</h3>
    341. 

  341. 

  342. March 10, 2006: added DUMA, contributed by Koneru Srikanth
    343. 

  343. <br>
    344. 

  344. Oct 6, 2003: mention of mpatrol
    345. 

  345. <br>
    346. 

  346. Sept 29, 2003: added dmalloc
    347. 

  347. <br>
    348. 

  348. June 25, 2003: minor change in the text
    349. 

  349. <br>
    350. 

  350. June 24, 2003: corrected result for memwatch's wrong1.c, added wrong7.c
    351. 

  351. <br>
    352. 

  352. June 15, 2003: initial release
    353. 

  353. <p>
    354. 

  354. 

  355. Please <a href="http://www.cs.utexas.edu/%7Ejpmartin/contact.html">contact</a> me if you have feedback or
    356. 

  356. would like to suggest another tool for the test.
    357. 

  357. 

  358. </p><p></p><hr>
    359. 

  359.  [<a accesskey="j" href="http://www.cs.utexas.edu/%7Ejpmartin/index.html"><b>J</b>P Martin</a>]
    360. 

  360.  [<a accesskey="s" href="http://www.cs.utexas.edu/%7Ejpmartin/resources.html">re<b>s</b>ources</a>]
    361. 

  361.  [<a accesskey="c" href="http://www.cs.utexas.edu/%7Ejpmartin/contact.html"><b>c</b>ontact information</a>]
    362. 

  362. <p>
    363. 

  363. </p><center>
    364. 

  364. <a href="http://www.anybrowser.org/campaign/"><img src="memCheckers-Dateien/viewed-any.gif" alt="Best viewed with *any* browser" border="0" height="30" width="85"></a>
    365. 

  365. </center>
    366. 

  366. 

  367. </body></html>
    368.