From: Luis Machado <luis.machado@arm.com>
To: Tom de Vries <tdevries@suse.de>, gdb-patches@sourceware.org
Subject: Re: [PATCH 2/2] [gdb/testsuite] Fix gdb.dwarf2/dw2-dir-file-name.exp for ppc64le
Date: Mon, 12 Sep 2022 11:20:00 +0100 [thread overview]
Message-ID: <ab864d79-02fa-58a2-ed89-6450d17cc60c@arm.com> (raw)
In-Reply-To: <20220901140905.24562-2-tdevries@suse.de>
On 9/1/22 15:09, Tom de Vries via Gdb-patches wrote:
> In commit cd919f5533c ("[gdb/testsuite] Fix
> gdb.dwarf2/dw2-dir-file-name.exp"), I made gdb.dwarf2/dw2-dir-file-name.exp
> independent of prologue analyzers, using this change:
> ...
> - gdb_breakpoint $func
> + gdb_breakpoint *$func
> ...
>
> That however caused a regression on ppc64le. For PowerPC, as described in the
> ELFv2 ABI, a function can have a global and local entry point.
>
> Setting a breakpoint on *$func effectively creates a breakpoint for the global
> entry point, so if the function is entered through the local entry point, the
> breakpoint doesn't trigger.
>
> Fix this by reverting commit cd919f5533c, and setting the breakpoint on
> ${func}_label instead.
>
> Tested on x86_64-linux and ppc64le-linux.
> ---
> gdb/testsuite/gdb.dwarf2/dw2-dir-file-name.exp | 8 ++++----
> gdb/testsuite/lib/gdb.exp | 7 +------
> 2 files changed, 5 insertions(+), 10 deletions(-)
>
> diff --git a/gdb/testsuite/gdb.dwarf2/dw2-dir-file-name.exp b/gdb/testsuite/gdb.dwarf2/dw2-dir-file-name.exp
> index 08b5c645fa2..053f7229537 100644
> --- a/gdb/testsuite/gdb.dwarf2/dw2-dir-file-name.exp
> +++ b/gdb/testsuite/gdb.dwarf2/dw2-dir-file-name.exp
> @@ -450,20 +450,20 @@ proc test { func compdir filename } {
> error "not absolute"
> }
>
> - gdb_breakpoint *$func
> + gdb_breakpoint ${func}_label
> gdb_continue_to_breakpoint $func "$func \\(\\) at .*"
>
> gdb_test_no_output "set filename-display absolute"
> verbose -log "expect: ${absolute}"
> - gdb_test "frame" "#0 $func \\(\\) at [string_to_regexp ${absolute}]:999" "absolute"
> + gdb_test "frame" " in $func \\(\\) at [string_to_regexp ${absolute}]:999" "absolute"
>
> gdb_test_no_output "set filename-display basename"
> verbose -log "expect: [file tail $filename]"
> - gdb_test "frame" "#0 $func \\(\\) at [string_to_regexp [file tail $filename]]:999" "basename"
> + gdb_test "frame" " in $func \\(\\) at [string_to_regexp [file tail $filename]]:999" "basename"
>
> gdb_test_no_output "set filename-display relative"
> verbose -log "expect: $filename"
> - gdb_test "frame" "#0 $func \\(\\) at [string_to_regexp $filename]:999" "relative"
> + gdb_test "frame" " in $func \\(\\) at [string_to_regexp $filename]:999" "relative"
> }
> }
>
> diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp
> index 17523f82996..2f1147159ad 100644
> --- a/gdb/testsuite/lib/gdb.exp
> +++ b/gdb/testsuite/lib/gdb.exp
> @@ -787,14 +787,9 @@ proc gdb_continue_to_breakpoint {name {location_pattern .*}} {
> global gdb_prompt
> set full_name "continue to breakpoint: $name"
>
> - set re_at_in " (at|in) "
> - if { [regexp $re_at_in $location_pattern] } {
> - set re_at_in " "
> - }
> -
> set kfail_pattern "Process record does not support instruction 0xfae64 at.*"
> gdb_test_multiple "continue" $full_name {
> - -re "(?:Breakpoint|Temporary breakpoint) .*$re_at_in$location_pattern\r\n$gdb_prompt $" {
> + -re "(?:Breakpoint|Temporary breakpoint) .* (at|in) $location_pattern\r\n$gdb_prompt $" {
> pass $full_name
> }
> -re "\[\r\n\]*(?:$kfail_pattern)\[\r\n\]+$gdb_prompt $" {
Looks like this makes the testsuite go from PASS to FAIL for aarch64. Are we still stopping in the first instruction and ignoring prologues?
next prev parent reply other threads:[~2022-09-12 10:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 14:09 [PATCH 1/2] [gdb/testsuite] Fix gdb.dwarf2/dw2-dir-file-name.exp with clang Tom de Vries
2022-09-01 14:09 ` [PATCH 2/2] [gdb/testsuite] Fix gdb.dwarf2/dw2-dir-file-name.exp for ppc64le Tom de Vries
2022-09-12 10:20 ` Luis Machado [this message]
2022-09-13 14:55 ` Tom de Vries
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=ab864d79-02fa-58a2-ed89-6450d17cc60c@arm.com \
--to=luis.machado@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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).