Blame SOURCES/0002-testsuite-Correct-syntax-for-gdb-backtrace-command.patch

11c2fb
From 91e3bc23a654e3daf1bf6546b06b9de7d00dbd59 Mon Sep 17 00:00:00 2001
11c2fb
From: Martin Kutlak <mkutlak@redhat.com>
11c2fb
Date: Fri, 29 Jun 2018 10:52:48 +0200
11c2fb
Subject: [PATCH] testsuite: Correct syntax for gdb backtrace command
11c2fb
11c2fb
The test failed on rawhide (gdb v8.1.50) with error message:
11c2fb
"A syntax error in expression, near `full'."
11c2fb
11c2fb
According to the GDB documentation the correct syntax for backtrace
11c2fb
command is `backtrace [full] n`.
11c2fb
11c2fb
- https://sourceware.org/gdb/onlinedocs/gdb/Backtrace.html
11c2fb
11c2fb
Signed-off-by: Martin Kutlak <mkutlak@redhat.com>
11c2fb
---
11c2fb
 tests/core_stacktrace.at | 2 +-
11c2fb
 1 file changed, 1 insertion(+), 1 deletion(-)
11c2fb
11c2fb
diff --git a/tests/core_stacktrace.at b/tests/core_stacktrace.at
11c2fb
index 7f6198e..13678c8 100644
11c2fb
--- a/tests/core_stacktrace.at
11c2fb
+++ b/tests/core_stacktrace.at
11c2fb
@@ -281,7 +281,7 @@ get_backtrace(const char *core_file, const char *executable)
11c2fb
   args[i++] = (char*)"-ex";
11c2fb
   args[i++] = sr_asprintf("core-file %s", core_file);
11c2fb
   args[i++] = (char*)"-ex";
11c2fb
-  args[i++] = (char*)"thread apply all -ascending backtrace 1024 full";
11c2fb
+  args[i++] = (char*)"thread apply all -ascending backtrace full 1024";
11c2fb
   args[i++] = (char*)"-ex";
11c2fb
   args[i++] = (char*)"info sharedlib";
11c2fb
   args[i++] = (char*)"-ex";
11c2fb
-- 
11c2fb
2.17.1
11c2fb