From: Tom de Vries <tdevries@suse.de>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH][gdb/testsuite] Fix gdb.go/methods.exp
Date: Tue, 25 Feb 2020 07:24:00 -0000 [thread overview]
Message-ID: <d82afc5a-6119-ef2e-4bbf-35b6d68bc063@suse.de> (raw)
In-Reply-To: <6639484a-4c7d-83e9-1d7b-66a3ed2066e6@suse.de>
[-- Attachment #1: Type: text/plain, Size: 392 bytes --]
[Fix ENOPATCH]
On 25-02-2020 08:23, Tom de Vries wrote:
> On 21-02-2020 19:36, Tom Tromey wrote:
>>>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
>>
>> Tom> I managed using maintenance print symbols.
>>
>> Tom> OK for trunk like this?
>>
>> Yes, thank you.
>>
>
> The gcc PR for which I added the xfail was closed, so this updates the
> gdb test-case.
>
> Committed as obvious.
>
[-- Attachment #2: 0001-gdb-testsuite-Remove-gcc-93866-xfail-in-methods.exp.patch --]
[-- Type: text/x-patch, Size: 2336 bytes --]
[gdb/testsuite] Remove gcc/93866 xfail in methods.exp
The test-case gdb.go/methods.exp contains an xfail for PR gcc/93866.
However, that PR has been marked resolved-wontfix, with clarification that the
gccgo symbol names for methods are correct, even if they're not the same as
for gc.
Remove the xfail.
Tested on x86_64-linux with gccgo-10.
gdb/testsuite/ChangeLog:
2020-02-25 Tom de Vries <tdevries@suse.de>
PR go/18926
* gdb.go/methods.exp: Remove gcc/93866 xfail.
---
gdb/testsuite/gdb.go/methods.exp | 17 ++++++++---------
1 file changed, 8 insertions(+), 9 deletions(-)
diff --git a/gdb/testsuite/gdb.go/methods.exp b/gdb/testsuite/gdb.go/methods.exp
index b24ee14cf2..068212044c 100644
--- a/gdb/testsuite/gdb.go/methods.exp
+++ b/gdb/testsuite/gdb.go/methods.exp
@@ -29,8 +29,7 @@ if { [prepare_for_testing "failed to prepare" ${testfile} ${srcfile} {debug go}]
}
set bp_location1 {main.T.Foo}
-set bp_location2 {main.(*T).Bar}
-set bp_location2_regexp {main.\(\*T\).Bar}
+set bp_location2 {main.T.Bar}
if { [go_runto_main] < 0 } {
untested "could not run to main"
@@ -49,7 +48,6 @@ gdb_test_multiple "maintenance print symbols" "" {
exp_continue
}
-re "^\r\n void main.T.Bar\[^\r\n\]*(?=\r\n)" {
- set found_wrong_bar 2
exp_continue
}
-re "\r\n$gdb_prompt $" {
@@ -86,20 +84,21 @@ if { $found_wrong_bar == 1 } {
# <1><528>: Abbrev Number: 19 (DW_TAG_subprogram)
# <529> DW_AT_name : main.Bar.pN6_main.T
setup_xfail "*-*-*"
-} elseif { $found_wrong_bar == 2 } {
+} else {
# We have with gccgo-8/9/10:
# <1><6e4>: Abbrev Number: 24 (DW_TAG_subprogram)
# <6e5> DW_AT_name : main.Bar..1main.T
# <6ec> DW_AT_linkage_name: main.T.Bar
- # xfail for GCC PR93866
- setup_xfail "*-*-*"
-} else {
+
# For reference: with go1.11.13:
# <1><6c49a>: Abbrev Number: 2 (DW_TAG_subprogram)
# <6c49b> DW_AT_name : main.(*T).Bar
- }
+
+ # It has been clarified in PR gcc/93866 that it's ok that symbols names
+ # diverge between gc and gccgo. So, we accept the main.T.Bar as valid.
+}
if { [gdb_breakpoint ${bp_location2} message] } {
- gdb_test "cont" "Breakpoint .*, ${bp_location2_regexp}.*" \
+ gdb_test "cont" "Breakpoint .*, ${bp_location2}.*" \
"going to second breakpoint"
}
next prev parent reply other threads:[~2020-02-25 7:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 11:02 Tom de Vries
2020-02-21 14:54 ` Tom Tromey
2020-02-21 16:17 ` Tom de Vries
2020-02-21 18:36 ` Tom Tromey
2020-02-25 7:23 ` Tom de Vries
2020-02-25 7:24 ` Tom de Vries [this message]
2020-02-25 13:07 ` 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=d82afc5a-6119-ef2e-4bbf-35b6d68bc063@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