[mythtv] malloc(): memory corruption -> how to proceed?

[Stuart Auchterlonie]

Stuart Auchterlonie wrote:
> Michael Rice wrote:
>> I get these assertions quite frequently (currently using SVN 14795).
>> I've attached the last few for a sampling.
>> I am assuming this error happens when the corruption is detected not
>> when the bad write occurs.  That makes
>> the stack traces not very useful in finding the problem.
>>
>> Any hints on how to track this down?  Is there a some way to configure
>> malloc to do more checking to get
>> a trace closer to the real problem?
>>
>> I tried compiling with mudflaps but that just seemed to hang.
>> I am guessing valgrind would be too slow on the backend.
>>
> 
> valgrind is the way forward.
> 
> if you need help with valgrind, join us in IRC but the basic incantation
> you will need is...
> 
> valgrind --tool=memcheck --error-limit=no --leak-check=full 
> --log-file=backend-valgrind.log -v -- /usr/local/bin/mythbackend | tee 
> backend.log
> 
> 

Oh and one more thing. Make sure you've done a make distclean and then
rebuilt it. That's the first thing to try when you have oddities like this.

Stuart