Fix test breakage caused by r9694.

git-svn-id: svn://svn.valgrind.org/valgrind/trunk@9697

diff --git a/coregrind/m_signals.c b/coregrind/m_signals.c
index a3f879a4ba4088957b21381a573a28f28d990dcb..f51d130fe2b6d3f4fde59c16b5d5033550b12674 100644 (file)
--- a/coregrind/m_signals.c
+++ b/coregrind/m_signals.c
@@ -1330,10 +1330,10 @@ static void default_action(const vki_siginfo_t *info, ThreadId tid)
       if (sigNo == VKI_SIGSEGV 
           && info && is_signal_from_kernel(info->si_code)
           && info->si_code == VKI_SEGV_MAPERR) {
-         VG_UMSG("If you believe this happened as a result of a stack" );
-         VG_UMSG("overflow in your program's main thread (unlikely but");
-         VG_UMSG("possible), you can try to increase the size of the"  );
-         VG_UMSG("main thread stack using the --main-stacksize= flag." );
+         VG_UMSG(" If you believe this happened as a result of a stack" );
+         VG_UMSG(" overflow in your program's main thread (unlikely but");
+         VG_UMSG(" possible), you can try to increase the size of the"  );
+         VG_UMSG(" main thread stack using the --main-stacksize= flag." );
          // FIXME: assumes main ThreadId == 1
          if (VG_(is_valid_tid)(1)) {
             VG_UMSG(" The main thread stack size used in this run was %d.",

diff --git a/memcheck/tests/addressable.stderr.exp b/memcheck/tests/addressable.stderr.exp
index ad76e96c7e78060d1e93e52e1c4c915fea4038cb..e000d04ef368d82435595dd3cc67678a726f3a71 100644 (file)
--- a/memcheck/tests/addressable.stderr.exp
+++ b/memcheck/tests/addressable.stderr.exp
@@ -19,9 +19,10 @@ Process terminating with default action of signal N (SIGSEGV or SIGBUS)
  Bad memory (SIGSEGV or SIGBUS) at address 0x........
    at 0x........: test2 (addressable.c:51)
    by 0x........: main (addressable.c:125)
- 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.
+ 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 ....
 
 ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 0 from 0)

diff --git a/memcheck/tests/badjump.stderr.exp b/memcheck/tests/badjump.stderr.exp
index 9187d7221719b670a0816c4ff97b51556db3825f..eddcd384054f3cfee5eec7b920a0a2fe21bd55bc 100644 (file)
--- a/memcheck/tests/badjump.stderr.exp
+++ b/memcheck/tests/badjump.stderr.exp
@@ -8,9 +8,10 @@ Process terminating with default action of signal 11 (SIGSEGV)
  Access not within mapped region at address 0x........
    at 0x........: ???
    by 0x........: (below main)
- 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.
+ 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 ....
 
 ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)

diff --git a/memcheck/tests/supp_unknown.stderr.exp b/memcheck/tests/supp_unknown.stderr.exp
index 1d4bfa5cfcc1707b01a998bfdbde4a95b9d22153..a176358e83031d3d3236df01f42b7962c946265e 100644 (file)
--- a/memcheck/tests/supp_unknown.stderr.exp
+++ b/memcheck/tests/supp_unknown.stderr.exp
@@ -3,7 +3,8 @@ Process terminating with default action of signal 11 (SIGSEGV)
  Access not within mapped region at address 0x........
    at 0x........: ???
    by 0x........: (below main)
- 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.
+ 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 ....

diff --git a/none/tests/linux/blockfault.stderr.exp b/none/tests/linux/blockfault.stderr.exp
index bb9f8f24f02c425bf4687c3140075fbf0d02fc00..b57c03735f17fb60e90da16c992009b1ebaac905 100644 (file)
--- a/none/tests/linux/blockfault.stderr.exp
+++ b/none/tests/linux/blockfault.stderr.exp
@@ -3,8 +3,9 @@
 Process terminating with default action of signal 11 (SIGSEGV)
  Access not within mapped region at address 0x........
    at 0x........: main (blockfault.c:30)
- 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.
+ 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 ....