[Valgrind-developers] valgrind: r9697 - in trunk: coregrind memcheck/tests none/tests/linux

[<sv...@va...>]

Author: njn
Date: 2009-04-30 06:09:09 +0100 (Thu, 30 Apr 2009)
New Revision: 9697

Log:
Fix test breakage caused by r9694.



Modified:
   trunk/coregrind/m_signals.c
   trunk/memcheck/tests/addressable.stderr.exp
   trunk/memcheck/tests/badjump.stderr.exp
   trunk/memcheck/tests/supp_unknown.stderr.exp
   trunk/none/tests/linux/blockfault.stderr.exp


Modified: trunk/coregrind/m_signals.c
===================================================================
--- trunk/coregrind/m_signals.c	2009-04-30 04:38:31 UTC (rev 9696)
+++ trunk/coregrind/m_signals.c	2009-04-30 05:09:09 UTC (rev 9697)
@@ -1330,10 +1330,10 @@
       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.",

Modified: trunk/memcheck/tests/addressable.stderr.exp
===================================================================
--- trunk/memcheck/tests/addressable.stderr.exp	2009-04-30 04:38:31 UTC (rev 9696)
+++ trunk/memcheck/tests/addressable.stderr.exp	2009-04-30 05:09:09 UTC (rev 9697)
@@ -19,9 +19,10 @@
  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)

Modified: trunk/memcheck/tests/badjump.stderr.exp
===================================================================
--- trunk/memcheck/tests/badjump.stderr.exp	2009-04-30 04:38:31 UTC (rev 9696)
+++ trunk/memcheck/tests/badjump.stderr.exp	2009-04-30 05:09:09 UTC (rev 9697)
@@ -8,9 +8,10 @@
  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)

Modified: trunk/memcheck/tests/supp_unknown.stderr.exp
===================================================================
--- trunk/memcheck/tests/supp_unknown.stderr.exp	2009-04-30 04:38:31 UTC (rev 9696)
+++ trunk/memcheck/tests/supp_unknown.stderr.exp	2009-04-30 05:09:09 UTC (rev 9697)
@@ -3,7 +3,8 @@
  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 ....

Modified: trunk/none/tests/linux/blockfault.stderr.exp
===================================================================
--- trunk/none/tests/linux/blockfault.stderr.exp	2009-04-30 04:38:31 UTC (rev 9696)
+++ trunk/none/tests/linux/blockfault.stderr.exp	2009-04-30 05:09:09 UTC (rev 9697)
@@ -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 ....