From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [committed][gdb/testsuite] Make gdb.dwarf2/dw2-line-number-zero.exp more robust
Date: Wed, 29 Jul 2020 08:42:12 +0200 [thread overview]
Message-ID: <20200729064211.GA18298@delia> (raw)
Hi,
On aarch64, there are FAILs for gdb.dwarf2/dw2-line-number-zero.exp due to
problems in the prologue analyzer (filed as PR26310).
Make the test-case more robust by avoiding to use the prologue analyzer:
...
-gdb_breakpoint "bar1"
+gdb_breakpoint "$srcfile:27"
...
Tested on x86_64-linux.
Committed to trunk.
Thanks,
- Tom
[gdb/testsuite] Make gdb.dwarf2/dw2-line-number-zero.exp more robust
gdb/testsuite/ChangeLog:
2020-07-29 Tom de Vries <tdevries@suse.de>
* gdb.dwarf2/dw2-line-number-zero.exp: Set breakpoints on lines
rather than function name.
---
gdb/testsuite/gdb.dwarf2/dw2-line-number-zero.exp | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gdb/testsuite/gdb.dwarf2/dw2-line-number-zero.exp b/gdb/testsuite/gdb.dwarf2/dw2-line-number-zero.exp
index a39256c171..12011b5f9c 100644
--- a/gdb/testsuite/gdb.dwarf2/dw2-line-number-zero.exp
+++ b/gdb/testsuite/gdb.dwarf2/dw2-line-number-zero.exp
@@ -115,13 +115,13 @@ if ![runto_main] {
return -1
}
-gdb_breakpoint "bar1"
+gdb_breakpoint "$srcfile:27"
gdb_continue_to_breakpoint "bar1" "\[^\r\n\]*:27\r\n.*"
gdb_test "n" "foo \\(2\\);" "bar1, 1st next"
gdb_test "n" "foo \\(4\\);" "bar1, 2nd next"
-gdb_breakpoint "bar2"
+gdb_breakpoint "$srcfile:41"
gdb_continue_to_breakpoint "bar2" "\[^\r\n\]*:41\r\n.*"
gdb_test "n" "foo \\(2\\);" "bar2, 1st next"
reply other threads:[~2020-07-29 6:42 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=20200729064211.GA18298@delia \
--to=tdevries@suse.de \
--cc=gdb-patches@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: 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