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

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