|
From: <sv...@va...> - 2008-05-22 14:44:33
|
Author: bart Date: 2008-05-22 15:44:39 +0100 (Thu, 22 May 2008) New Revision: 8119 Log: Filter out thread stack size. Modified: branches/CROSS_COMPILATION/none/tests/blockfault.stderr.exp branches/CROSS_COMPILATION/none/tests/filter_stderr Modified: branches/CROSS_COMPILATION/none/tests/blockfault.stderr.exp =================================================================== --- branches/CROSS_COMPILATION/none/tests/blockfault.stderr.exp 2008-05-22 14:30:33 UTC (rev 8118) +++ branches/CROSS_COMPILATION/none/tests/blockfault.stderr.exp 2008-05-22 14:44:39 UTC (rev 8119) @@ -6,5 +6,5 @@ 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 .... Modified: branches/CROSS_COMPILATION/none/tests/filter_stderr =================================================================== --- branches/CROSS_COMPILATION/none/tests/filter_stderr 2008-05-22 14:30:33 UTC (rev 8118) +++ branches/CROSS_COMPILATION/none/tests/filter_stderr 2008-05-22 14:44:39 UTC (rev 8119) @@ -8,5 +8,7 @@ sed "/^Nulgrind, a binary JIT-compiler./ , /./ d" | # Anonymise addresses -$dir/../../tests/filter_addresses +$dir/../../tests/filter_addresses | +# 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 .../" |