zenithsiz/ftmemsim-valgrind
1
0
Fork 0
mirror of https://github.com/Zenithsiz/ftmemsim-valgrind.git synced 2026-02-03 18:13:01 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Fix test breakage caused by r9694.

Browse Source 
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@9697
This commit is contained in:
Nicholas Nethercote 2009-04-30 05:09:09 +00:00
parent 9c937e19b9
commit af09b2fa03
5 changed files with 20 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
coregrind/m_signals.c
View File

@ -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.",

7
memcheck/tests/addressable.stderr.exp
View File

@ -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)

7
memcheck/tests/badjump.stderr.exp
View File

@ -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)

7
memcheck/tests/supp_unknown.stderr.exp
View File

@ -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 ....

7
none/tests/linux/blockfault.stderr.exp
View File

@ -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 ....