Comment 3 for bug 639687

The backtrace is a mess. Somehow something breaks while loading the GNU Octave m-files? During a delete on an octave-base-value object? I don't know where to begin on this one.

Looking at what you got that time before this:
free(): invalid pointer: 0xb72e1930
Hm. 0xb7....? That's a pointer to something dangerously close to the stack. What is it doing inside a free call? Am I missing something?

I'd say try running octave-tip or the testing version. I don't recognize this specific error, but 3.2.4 is 8 months old. Many things have been fixed and I don't remember them all.