On Wed, 8 Sep 2004, Jon A. Cruz wrote:
Can you try valgrind? In general I've had much better luck with that. (It also catches many things that EF doesn't)
livarot sets valgrind screaming, but previous attempts to fix livarot had broken it (more) horribly and we had to revert the changes.
The livarot warnings are mostly harmless (uninitialized data which is copied, but never actually used), but they drown out anything else that might be going on.
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.
I am trying to fix it again, taking a more gradual approach this time.
-mental