From b77e045e1fd3e699ce4c0e4969ef1f19e6da35ae Mon Sep 17 00:00:00 2001 From: Florian Krohm Date: Sat, 7 Mar 2015 12:49:32 +0000 Subject: [PATCH] Rewritten to use a single line instead of line splicing to avoid line number differences in the reported error. git-svn-id: svn://svn.valgrind.org/valgrind/trunk@14988 --- none/tests/linux/stack-overflow.c | 8 ++------ none/tests/linux/stack-overflow.stderr.exp | 2 +- 2 files changed, 3 insertions(+), 7 deletions(-) diff --git a/none/tests/linux/stack-overflow.c b/none/tests/linux/stack-overflow.c index 86f9e4af8b..0ebbfbb8b2 100644 --- a/none/tests/linux/stack-overflow.c +++ b/none/tests/linux/stack-overflow.c @@ -1,9 +1,5 @@ /* There should be a user message about the overflow. - Wrtten in a single line so there is no confusion on what line + Written in a single line so there is no confusion on what line the overflow occurs. */ -int main(int argc, char *argv[]) \ -{ \ - volatile int arr[1000]; \ - return main(arr[argc%2], 0); \ -} +int main(int argc, char *argv[]) { volatile int arr[1000]; return main(arr[argc%2], 0); } diff --git a/none/tests/linux/stack-overflow.stderr.exp b/none/tests/linux/stack-overflow.stderr.exp index b1f26ac007..dd5e595153 100644 --- a/none/tests/linux/stack-overflow.stderr.exp +++ b/none/tests/linux/stack-overflow.stderr.exp @@ -4,7 +4,7 @@ Stack overflow in thread #1: can't grow stack to 0x........ Process terminating with default action of signal 11 (SIGSEGV) Access not within mapped region at address 0x........ Stack overflow in thread #1: can't grow stack to 0x........ - at 0x........: main (stack-overflow.c:6) + at 0x........: main (stack-overflow.c: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 -- 2.47.3