How to debug “glibc detected *** python: malloc(): memory corruption”?

I'd hazard a guess that your code is overflowing an array somewhere (or causing Python to do so).

I'd hazard a guess that your code is overflowing an array somewhere (or causing Python to do so). You're going to find debugging this to be hard if you can't reliably reproduce it, so you might want to explicitly seed your random number generator and try to find a seed with which you can reproduce the corruption. You might also find that using a tool like valgrind is helpful to track when you write over the limits of an allocation -- probably more so when you can reproduce it every time.

1 +1 for valgrind – bstpierre Sep 3 '10 at 19:04.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.