|
From: Erik C. <er...@ar...> - 2003-08-05 10:22:53
|
On Tue, Aug 05, 2003 at 11:02:03AM +0100, Nicholas Nethercote wrote:
>
> > Especially the second leads to a really bad behaviour by dumping your
> > memory.
>
> Well, the array overruns not detected by Valgrind will never cause a seg
> fault.
Not true:
void f()
{
char a[4];
int *b;
int c;
b = &c;
a[5] = 123;
*b = 456;
}
valgrind will tell you that the write through b is a problem,
but the real reason is the array overrun which valgrind cannot
detect, but which (indirectly) causes an array overrun.
I don't think there's any way to fix this in valgrind. Perhaps
this: http://web.inter.nl.net/hcc/Haj.Ten.Brugge/ is what the
original poster wants. Or perhaps Java is what he really wants.
--
Erik Corry er...@ar...
|