Output of valgrind's memcheck running 0AD

[Heron]

Hi,

I encountered a segfault just after reloading a map (reproducible). Because it seemed to be caused by a buffer over/underflow, I ran 0AD under memcheck memcheck. There where more than a million of fglrx-driver errors (ati-driver for linux) in the output, so I wrote a small script to remove those. Keep in mind: it's possible, but rather improbable, that the script removes also some non-fglrx-related error messages.

See the attachment for the cleaned-up output.

logfile_clean.txt

[Ykkrosh]

(You can use Valgrind's suppression files to remove spurious results.)

Looks like the main problem is that it's trying to use an entity after it's been deleted, which is a reasonably common problem with the old simulation system (since there's lots of pointers and a lack of robustness in the design). I'm currently working on rewriting the entire simulation system, partly due to this kind of thing, so these problems should go away (the new design tries to minimise the chances for these errors, and also has a lot more automated tests), so I think I'd be happy to ignore this problem for now.