|
From: Jean P. <2s...@ma...> - 2004-09-06 23:15:54
|
On Tue, 07 Sep 2004 00:07:46 +0100, Tom Hughes <th...@cy...> wrote : > > One bug I found very annoying is this one : > > > > double array[3]; > > array[3] = 0; > > > > And it seems that valgrind doesn't detect this one. > > It can't really do so - no run time only system can. The only systems > that detect that problem are those that do compile time manipulations > to either add bounds checking or insert guard words between the stack > variables. > Thanks for your answer. I'm stuck with Insure++ and gcc bounds-checking then... |