Runtime security/memory checks for gcc/gdb

[Shachar Shemesh]

Elazar Leibovich wrote:
> I tried using valgrind in a different project. The main problems I've 
> had with valgrind are speed
Yes, that is known.
> and false positives.
That one is new to me. Can you elaborate?
> Getting gdb to report that during runtime has its advantages.
> Anyhow, I was hoping to hear about products/valgrind add-ons etc I do 
> not know.
>
> 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...
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.

I'm not sure at which version this started, but gcc 4.4.2 with -Wextra 
catches your second example (array bounds problem).

Shachar

-- 
Shachar Shemesh
Lingnu Open Source Consulting Ltd.
http://www.lingnu.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.cs.huji.ac.il/pipermail/linux-il/attachments/20100112/1677646d/attachment.html>