public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Tom de Vries <vries@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] [gdb/testsuite] Fix language in dw2-bad-mips-linkage-name.exp Date: Fri, 24 Apr 2020 21:25:47 +0000 (GMT) [thread overview] Message-ID: <20200424212547.63E69389365C@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=7cf288744fdd238bbab079a53584f76181d44218 commit 7cf288744fdd238bbab079a53584f76181d44218 Author: Tom de Vries <tdevries@suse.de> Date: Fri Apr 24 23:25:44 2020 +0200 [gdb/testsuite] Fix language in dw2-bad-mips-linkage-name.exp The test-case gdb.dwarf2/dw2-bad-mips-linkage-name.exp has a CU with language C, which contains a subprogram with a C++-mangled name as its DW_AT_mips_linkage_name attribute. Fix this by changing the language of the CU to C++. Tested on x86_64-linux. gdb/testsuite/ChangeLog: 2020-04-24 Tom de Vries <tdevries@suse.de> * gdb.dwarf2/dw2-bad-mips-linkage-name.exp: Set language of CU to C++. Diff: --- gdb/testsuite/ChangeLog | 5 +++++ gdb/testsuite/gdb.dwarf2/dw2-bad-mips-linkage-name.exp | 6 +++--- 2 files changed, 8 insertions(+), 3 deletions(-) diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog index 3458a54c535..ba79290e114 100644 --- a/gdb/testsuite/ChangeLog +++ b/gdb/testsuite/ChangeLog @@ -1,3 +1,8 @@ +2020-04-24 Tom de Vries <tdevries@suse.de> + + * gdb.dwarf2/dw2-bad-mips-linkage-name.exp: Set language of CU to + C++. + 2020-04-24 Tom Tromey <tromey@adacore.com> * gdb.ada/frame_arg_lang.exp: Run with multiple -fgnat-encodings diff --git a/gdb/testsuite/gdb.dwarf2/dw2-bad-mips-linkage-name.exp b/gdb/testsuite/gdb.dwarf2/dw2-bad-mips-linkage-name.exp index d00308a5702..5f01c41aaa3 100644 --- a/gdb/testsuite/gdb.dwarf2/dw2-bad-mips-linkage-name.exp +++ b/gdb/testsuite/gdb.dwarf2/dw2-bad-mips-linkage-name.exp @@ -38,7 +38,7 @@ Dwarf::assemble $asm_file { cu {} { DW_TAG_compile_unit { - {DW_AT_language @DW_LANG_C} + {DW_AT_language @DW_LANG_C_plus_plus} {DW_AT_name dw2-bad-mips-linkage-name.c} {DW_AT_comp_dir /tmp} @@ -78,5 +78,5 @@ if { [prepare_for_testing "failed to prepare" ${testfile} \ # much matter what we test here, so long as we do something to make # sure that the DWARF is read. -gdb_test "ptype f" " = bool \\(\\)" -gdb_test "ptype g" " = bool \\(\\)" +gdb_test "ptype f" " = bool \\(void\\)" +gdb_test "ptype g" " = bool \\(void\\)"
reply other threads:[~2020-04-24 21:25 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20200424212547.63E69389365C@sourceware.org \ --to=vries@sourceware.org \ --cc=gdb-cvs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).