Bläddra i källkod

Fix documentation of STARPU_WATCHDOG_CRASH, document typing handle SIGABRT nopass in gdb

Samuel Thibault 11 år sedan
förälder
incheckning
d711867861

+ 3 - 2
doc/doxygen/chapters/05check_list_performance.doxy

@@ -100,8 +100,9 @@ any task for 10ms. In addition to that,
 
 <c>export STARPU_WATCHDOG_CRASH=1</c>
 
-triggers a crash in that condition, thus allowing to catch the situation in gdb
-etc.
+raises SIGABRT in that condition, thus allowing to catch the situation in gdb.
+It can also be useful to type "handle SIGABRT nopass" in gdb to be able to let
+the process continue, after inspecting the state of the process.
 
 \section HowToLimitMemoryPerNode How to limit memory per node
 

+ 1 - 1
doc/doxygen/chapters/40environment_variables.doxy

@@ -587,7 +587,7 @@ end of the execution of an application (\ref DataStatistics).
 \anchor STARPU_WATCHDOG_TIMEOUT
 \addindex __env__STARPU_WATCHDOG_TIMEOUT
 When set to a value other than 0, allows to make StarPU print an error
-message whenever StarPU does not terminate any task for 10ms. Should
+message whenever StarPU does not terminate any task for the given time (in µs). Should
 be used in combination with \ref STARPU_WATCHDOG_CRASH (see \ref
 DetectionStuckConditions).
 </dd>