X-Git-Url: http://info.iut-bm.univ-fcomte.fr/pub/gitweb/simgrid.git/blobdiff_plain/1152cce9809624951ac25988b515c34f3e068bf8..8c1d7d0a4f5a0b9531f158505527a4f2a4db3e70:/doc/doxygen/options.doc

diff --git a/doc/doxygen/options.doc b/doc/doxygen/options.doc
index d7d608c6c1..82776a5768 100644
--- a/doc/doxygen/options.doc
+++ b/doc/doxygen/options.doc
@@ -392,7 +392,9 @@ to the most effient:
 
 The only reason to change this setting is when the debugging tools get
 fooled by the optimized context factories. Threads are the most
-debugging-friendly contextes.
+debugging-friendly contextes, as they allow to set breakpoints anywhere with gdb
+ and visualize backtraces for all processes, in order to debug concurrency issues.
+Valgrind is also more comfortable with threads, but it should be usable with all factories.
 
 \subsection options_virt_stacksize Adapting the used stack size
 
@@ -417,7 +419,7 @@ model checker (see \ref options_mc_perf).
 
 In some cases, no stack guard page is used and the stack will silently
 overflow on other parts of the memory if the stack size is too small
-for your application. This happens :
+for your application. This happens :
 
 - on Windows systems;
 - when the model checker is enabled;