MenTaLguY wrote:
When I attempted to fix that, I did eventually manage to get rid of the uninitialized value warnings, but livarot had also stopped working. I don't know if the remainder of the valgrind warnings (e.g. out of bounds array accesses) at that point were my fault or fred's.
Ooooh. That's possibly bad.
(BTW, this is for the benefit of others, Mental is pretty up on these things)
The most likely thing is some accidental change that broke things.
However... in clearing up warnings of that type, it's possible that some buggy behavior was depended on, and cleaning things up properly "broke" some work-around that was elsewhere. Or just some sloppy code that just accidentally worked.
I am trying to fix it again, taking a more gradual approach this time.
Always good.
Of course, getting everyone possible to join in on "zero-warnings" is a good goal. Sometimes we have to be realistic about hitting it, but keeping it in mind helps get there slow and steady.