From: Augustin Degomme <degomme@idpann.imag.fr>
Date: Thu, 30 Jan 2014 16:57:09 +0000 (+0100)
Subject: add link + fix doc
X-Git-Tag: v3_11_beta~104
X-Git-Url: http://info.iut-bm.univ-fcomte.fr/pub/gitweb/simgrid.git/commitdiff_plain/2cd53ff8c7476e05db7465c126fbdb77d609d3bf

add link + fix doc
---

diff --git a/doc/doxygen/options.doc b/doc/doxygen/options.doc
index 9f5fa98985..304781edd8 100644
--- a/doc/doxygen/options.doc
+++ b/doc/doxygen/options.doc
@@ -390,8 +390,8 @@ stacks), leading to segfaults with corrupted stack traces.
 
 If you want to push the scalability limits of your code, you really
 want to reduce the \b contexts/stack_size item. Its default value
-is 128 (in Kib), while our Chord simulation works with stacks as small
-as 16 Kib, for example. For the thread factory, the default value 
+is 128 (in KiB), while our Chord simulation works with stacks as small
+as 16 KiB, for example. For the thread factory, the default value 
 is the one of the system, if it is too large/small, it has to be set 
 with this parameter.
 
diff --git a/src/smpi/smpirun.in b/src/smpi/smpirun.in
index 842448ab70..734a837f0a 100755
--- a/src/smpi/smpirun.in
+++ b/src/smpi/smpirun.in
@@ -420,7 +420,9 @@ fi
 ${EXEC} ${TRACEOPTIONS} ${SIMOPTS} ${PLATFORMTMP} ${APPLICATIONTMP}
 status=$?
 
-if [[ $status -eq 139 ]]; then echo "ERROR: A segmentation fault was triggered. A common in simgrid cause may be the use of a too small stack size for the simulated processes (default 128KB), please see contexts/stack_size parameter"; fi
+if [[ $status -eq 139 ]]; then echo "ERROR: A segmentation fault was triggered. 
+A common cause in SimGrid may be the use of a too small stack size for the simulated processes (default 128KiB).
+Please see contexts/stack_size parameter , or http://simgrid.org/simgrid/latest/doc/options.html#options_virt_stacksize "; fi
 
 if [ -z "${KEEP}" ] ; then
    if [ -z "${PLATFORM}" ]; then