+
+
+*
+* SimGrid Hacker Survival Guide (FIXME: should be betterly placed)
+********************************
+
+* Before pushing any change, don't forget to check if the compilation
+ passes with compiler optimizations and warnings turned on:
+ cmake -Denable_compile_optimizations=ON \
+ -Denable_compile_warnings=ON
+
+* Your commit message should follow the git habits, explained eg here:
+ http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
+
+* When you add/remove files, and/or make changes in the lists of files to build,
+ please check that "make distcheck" still succeeds. This is needed to ensure
+ that the generated archive is consistent.
+
+* If you want to debug memory allocation problems, here are a few hints:
+ - disable compiler optimizations, to have better backtraces;
+ - disable the mallocators, or it will be hard to match malloc's with
+ free's;
+ - disable model checking, unless your problem lies in the model
+ checker part of SimGrid (MC brings its own malloc implementation,
+ which valgrind doesn't understand).
+ All this is configured with:
+ cmake -Denable_model-checking=OFF \
+ -Denable_mallocators=OFF \
+ -Denable_compile_optimizations=OFF
+
+* If you break the logs (for example while hacking in the dynars), you
+ want to define XBT_LOG_MAYDAY at the beginning of log.h. It will
+ deactivate the whole logging mechanism, switching to printfs
+ instead. SimGrid becomes incredibly verbose when doing so, but it
+ you let you fixing the dynars.