Browse Source

Document how to debug simgrid applications with gdb

Samuel Thibault 11 years ago
parent
commit
25d9b910d0
1 changed files with 8 additions and 0 deletions
  1. 8 0
      doc/doxygen/chapters/21simgrid.doxy

+ 8 - 0
doc/doxygen/chapters/21simgrid.doxy

@@ -121,6 +121,14 @@ case. Since during simgrid execution, the functions of the codelet are actually
 not called, one can use dummy functions such as the following to still permit
 not called, one can use dummy functions such as the following to still permit
 CUDA or OpenCL execution:
 CUDA or OpenCL execution:
 
 
+\section Debugging applications
+
+By default, simgrid uses its own implementation of threads, which prevents gdb
+from being able to inspect stacks of all threads.  To be able to fully debug an
+application running with simgrid, pass the <c>--cfg=contexts/factory:thread</c>
+option to the application, to make simgrid use system threads, which gdb will be
+able to manipulate as usual.
+
 \snippet simgrid.c To be included. You should update doxygen if you see this text.
 \snippet simgrid.c To be included. You should update doxygen if you see this text.