<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body dir="ltr" bgcolor="#ffffff" text="#000000">
Elazar Leibovich wrote:
<blockquote
cite="mid:2d6bb6c1001112148p197e4366n2e079c58c987e1d9@mail.gmail.com"
type="cite">
<div dir="ltr">I tried using valgrind in a different project. The
main problems I've had with valgrind are speed</div>
</blockquote>
Yes, that is known.<br>
<blockquote
cite="mid:2d6bb6c1001112148p197e4366n2e079c58c987e1d9@mail.gmail.com"
type="cite">
<div dir="ltr"> and false positives.</div>
</blockquote>
That one is new to me. Can you elaborate?<br>
<blockquote
cite="mid:2d6bb6c1001112148p197e4366n2e079c58c987e1d9@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>Getting gdb to report that during runtime has its advantages.</div>
<div>Anyhow, I was hoping to hear about products/valgrind add-ons etc
I do not know.</div>
<div><br>
<div>The main practical problem with it, is convincing management
that getting a linux box or VM and build the code on it is worth our
while...<br>
</div>
</div>
</div>
</blockquote>
Personally, I think that you should start with gcc. Just because it
spews out thousands of warnings does not mean they are not all
relevant. Compiler warnings are the easiest to fix, easiest to find,
and are often written off for no justifiable reason.<br>
<br>
I'm not sure at which version this started, but gcc 4.4.2 with -Wextra
catches your second example (array bounds problem).<br>
<br>
Shachar<br>
<pre class="moz-signature" cols="72">--
Shachar Shemesh
Lingnu Open Source Consulting Ltd.
<a class="moz-txt-link-freetext" href="http://www.lingnu.com">http://www.lingnu.com</a>
</pre>
</body>
</html>