From: Tom de Vries <tdevries@suse.de>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: [committed][gdb/testsuite] Fix language in dw2-bad-mips-linkage-name.exp
Date: Fri, 24 Apr 2020 23:27:24 +0200 [thread overview]
Message-ID: <59ad81da-61d8-e940-e5b1-dd479f03b5d6@suse.de> (raw)
In-Reply-To: <87ftcszk07.fsf@tromey.com>
[-- Attachment #1: Type: text/plain, Size: 847 bytes --]
[ was: Re: [PATCH 08/10] Use the linkage name if it exists ]
On 24-04-2020 22:50, Tom Tromey wrote:
>>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
>
> Tom> Hmm, one thing that is odd about this test-case is that it constructs a
> Tom> C language CU, which contains a subprogram with DW_AT_MIPS_linkage_name
> Tom> attribute with a C++ mangled name.
>
> This sounds very familiar. I feel like I patched this at some point but
> now I don't know where that patch went.
>
> Tom> If I update the testcase to use a c++ language CU, the test passes:
>
> I think this is the correct thing to do.
> The main point of the test is to ensure that the linkage name with the
> wrong form doesn't cause a crash:
>
> {DW_AT_MIPS_linkage_name 42 DW_FORM_data1}
>
> I suggest you check this in.
Ack, committed as attached below.
Thanks,
- Tom
[-- Attachment #2: 0001-gdb-testsuite-Fix-language-in-dw2-bad-mips-linkage-name.exp.patch --]
[-- Type: text/x-patch, Size: 1494 bytes --]
[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++.
---
gdb/testsuite/gdb.dwarf2/dw2-bad-mips-linkage-name.exp | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
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\\)"
next prev parent reply other threads:[~2020-04-24 21:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 20:07 [PATCH 00/10] Fix two name-related bugs in DWARF reader Tom Tromey
2020-03-25 20:07 ` [PATCH 01/10] Convert symbol_set_demangled_name to a method Tom Tromey
2020-03-25 20:07 ` [PATCH 02/10] Move the rust "{" hack Tom Tromey
2020-03-25 20:07 ` [PATCH 03/10] Fix two latent Rust bugs Tom Tromey
2020-03-25 20:07 ` [PATCH 04/10] Add attribute::value_as_string method Tom Tromey
2020-03-25 20:07 ` [PATCH 05/10] Introduce new add_psymbol_to_list overload Tom Tromey
2020-03-25 20:07 ` [PATCH 06/10] Use the " Tom Tromey
2020-03-25 20:07 ` [PATCH 07/10] Don't call compute_and_set_names for partial symbols Tom Tromey
2020-03-25 20:07 ` [PATCH 08/10] Use the linkage name if it exists Tom Tromey
2020-04-24 16:06 ` Tom de Vries
2020-04-24 18:09 ` Tom de Vries
2020-04-24 20:50 ` Tom Tromey
2020-04-24 21:27 ` Tom de Vries [this message]
2020-04-24 21:34 ` [committed][gdb/testsuite] Fix language in dw2-bad-mips-linkage-name.exp Tom Tromey
2020-03-25 20:07 ` [PATCH 09/10] Fix Rust test cases Tom Tromey
2020-03-25 20:07 ` [PATCH 10/10] Remove symbol_get_demangled_name Tom Tromey
2020-03-25 22:48 ` [PATCH 00/10] Fix two name-related bugs in DWARF reader Christian Biesinger
2020-03-25 23:50 ` Tom Tromey
2020-04-24 14:18 ` Tom de Vries
2020-04-24 14:45 ` Tom Tromey
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=59ad81da-61d8-e940-e5b1-dd479f03b5d6@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.com \
/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: link
Be 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).