On Thu, 5 May 2011, Riccardo (Jack) Lucchetti wrote:
> On Wed, 4 May 2011, Allin Cottrell wrote:
>
> > This is a cautionary tale: it can be more difficult that you'd
> > think, converting code from 1-based indexing to 0-based, when you
> > have nested loops to handle!
>
> As I said in my previous message, I find it quite odd that the problem
> hasn't surfaced in such a long time. Also mysterious is the failure by
> valgrind to detect it. Oh well.
It's odd, yes, but it's not something that valgrind is good at
catching: valgrind does a great job with memory allocated on the
"heap" (malloc) but doesn't help much with stack corruption.
Allin