[Numpy-discussion] segmentation fault
Stéfan van der Walt
Wed May 28 11:39:22 CDT 2008
2008/5/28 Hoyt Koepke <firstname.lastname@example.org>:
> In my experience tracking down these sorts of things, if the effect is
> delayed and detected by glibc, it almost always means that a few bytes
> beyond the end of the data part of an array have been overwritten.
> This causes glibc's memory management stuff to crash later on when the
> object is deallocated (or something like that). Of course, I should
> say I was doing the overwritting in my own c code...
If you look at the valgrind trace I sent earlier, you'll see that that
is the case.
More information about the Numpy-discussion