If you believe this happened as a result of a stack overflow in your
program's main thread (unlikely but possible), you can try to increase
the size of the main thread stack using the --main-stacksize= flag.
- The main thread stack size used in this run was 16777216.
+ The main thread stack size used in this run was ....
ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 0 from 0)
malloc/free: in use at exit: 0 bytes in 0 blocks.
If you believe this happened as a result of a stack overflow in your
program's main thread (unlikely but possible), you can try to increase
the size of the main thread stack using the --main-stacksize= flag.
- The main thread stack size used in this run was 16777216.
+ The main thread stack size used in this run was ....
ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
malloc/free: in use at exit: 0 bytes in 0 blocks.
If you believe this happened as a result of a stack overflow in your
program's main thread (unlikely but possible), you can try to increase
the size of the main thread stack using the --main-stacksize= flag.
- The main thread stack size used in this run was 16777216.
+ The main thread stack size used in this run was ....
ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
malloc/free: in use at exit: 0 bytes in 0 blocks.
# Anonymise line numbers in mc_replace_strmem.c
sed "s/mc_replace_strmem.c:[0-9]*/mc_replace_strmem.c:.../" |
+# Remove the size in "The main thread stack size..." message.
+sed "s/The main thread stack size used in this run was [0-9]*/The main thread stack size used in this run was .../" |
+
$dir/../../tests/filter_test_paths
If you believe this happened as a result of a stack overflow in your
program's main thread (unlikely but possible), you can try to increase
the size of the main thread stack using the --main-stacksize= flag.
- The main thread stack size used in this run was 16777216.
+ The main thread stack size used in this run was ....
ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
malloc/free: in use at exit: 0 bytes in 0 blocks.
If you believe this happened as a result of a stack overflow in your
program's main thread (unlikely but possible), you can try to increase
the size of the main thread stack using the --main-stacksize= flag.
- The main thread stack size used in this run was 16777216.
+ The main thread stack size used in this run was ....
Extra options read from ~/.valgrindrc, $VALGRIND_OPTS, ./.valgrindrc
- Valgrind is Copyright (C) 2000-2007 Julian Seward et al.
+ Valgrind is Copyright (C) 2000-2008 Julian Seward et al.
and licensed under the GNU General Public License, version 2.
Bug reports, feedback, admiration, abuse, etc, to: www.valgrind.org.
Extra options read from ~/.valgrindrc, $VALGRIND_OPTS, ./.valgrindrc
- Valgrind is Copyright (C) 2000-2007 Julian Seward et al.
+ Valgrind is Copyright (C) 2000-2008 Julian Seward et al.
and licensed under the GNU General Public License, version 2.
Bug reports, feedback, admiration, abuse, etc, to: www.valgrind.org.