Comment 9 for bug 1690519

crash1, 2 and 3 all seems different things to me.

The crashes in #5 and #6 seem to be the same, but also different to the first three.

The absolute best approaches I know off to figuring out where these memory violations come from is investigating using MSAN [1] and ASAN [2]. This requires building widelands and maybe its dependencies with these settings turned on in the compiler. Other approaches are:

- Mac OS ships with some memory debugging tools. [3]
- A simple library that replace malloc and gives some memory feedback is electric fence [4]
- valgrind's memcheck is also an excellent, but slow tool [5]

[1] https://clang.llvm.org/docs/MemorySanitizer.html
[2] https://clang.llvm.org/docs/AddressSanitizer.html
[3] https://developer.apple.com/library/content/documentation/Performance/Conceptual/ManagingMemory/Articles/MallocDebug.html
[4] https://en.wikipedia.org/wiki/Electric_Fence
[5] http://valgrind.org/docs/manual/mc-manual.html