From: Tom de Vries Date: Wed, 24 Oct 2018 07:49:44 +0000 (+0200) Subject: [gdb/testsuite] Handle removed valgrind option --db-attach X-Git-Tag: users/ARM/embedded-binutils-master-2018q4~366 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=4df46df7a4643c0f6f93a2739c4b7bc0e83bcdce;p=platform%2Fupstream%2Fbinutils.git [gdb/testsuite] Handle removed valgrind option --db-attach When running valgrind-db-attach.exp with valgrind version 3.13.0, we get: ... PASS: gdb.base/valgrind-db-attach.exp: spawn valgrind valgrind: Unknown option: --db-attach=yes valgrind: Use --help for more information or consult the user manual. ERROR: Process no longer exists UNRESOLVED: gdb.base/valgrind-db-attach.exp: valgrind started ... The valgrind option --db-attach has been deprecated in version 3.10.0, and removed in version 3.11.0. Fix valgrind-db-attach.exp to replace the ERROR/UNRESOLVED with: ... UNSUPPORTED: gdb.base/valgrind-db-attach.exp: valgrind started ... Tested on x86_64-linux. 2018-10-24 Tom de Vries * gdb.base/valgrind-db-attach.exp: Handle removed support for --db-attach in valgrind. --- diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog index 447578e..99d1e85 100644 --- a/gdb/testsuite/ChangeLog +++ b/gdb/testsuite/ChangeLog @@ -1,3 +1,8 @@ +2018-10-24 Tom de Vries + + * gdb.base/valgrind-db-attach.exp: Handle removed support for + --db-attach in valgrind. + 2018-10-23 Andrew Burgess * gdb.arch/riscv-reg-aliases.c: New file. diff --git a/gdb/testsuite/gdb.base/valgrind-db-attach.exp b/gdb/testsuite/gdb.base/valgrind-db-attach.exp index 3be6af5..3e40283 100644 --- a/gdb/testsuite/gdb.base/valgrind-db-attach.exp +++ b/gdb/testsuite/gdb.base/valgrind-db-attach.exp @@ -51,6 +51,10 @@ set use_gdb_stub 1 set test "valgrind started" # The trailing '.' differs for different memcheck versions. gdb_test_multiple "" $test { + -re "valgrind: Unknown option: --db-attach=yes" { + unsupported $test + return -1 + } -re "Memcheck, a memory error detector\\.?\r\n" { pass $test }