From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <vries@sourceware.org>
Received: by sourceware.org (Postfix, from userid 2205)
	id 4D59B3857C51; Mon, 28 Nov 2022 16:18:50 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4D59B3857C51
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1669652330;
	bh=G6Ksuo56Fg2Zny8NJeAByCJojIi19HL5RVwnrXqrT8Q=;
	h=From:To:Subject:Date:From;
	b=oXiP4zzr8bUHOW0zNA0KhoRZDqIyHruUURdzcWYwh66tX/2en9gYyKdeu282mEiPS
	 BImTq29kEtAsz86K3WOVk03baDt4qVOTHpI4eFSmloAbS8BRL85FGNcMpvQ5GNpEnH
	 Snroi1uvSeQPIIS/SFeE9jAeo+dlXj4HNVHBkraI=
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
From: Tom de Vries <vries@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] [gdb/testsuite] Fix gdb.ada/out_of_line_in_inlined.exp for ppc64le
X-Act-Checkin: binutils-gdb
X-Git-Author: Tom de Vries <tdevries@suse.de>
X-Git-Refname: refs/heads/master
X-Git-Oldrev: af31506c31a59a6edbb13498d6075fa704b801cd
X-Git-Newrev: b4bb9faa78c7454e9aafa4fbdbf76e4206acd14a
Message-Id: <20221128161850.4D59B3857C51@sourceware.org>
Date: Mon, 28 Nov 2022 16:18:50 +0000 (GMT)
List-Id: <gdb-cvs.sourceware.org>

https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3Db4bb9faa78c7=
454e9aafa4fbdbf76e4206acd14a

commit b4bb9faa78c7454e9aafa4fbdbf76e4206acd14a
Author: Tom de Vries <tdevries@suse.de>
Date:   Mon Nov 28 17:18:47 2022 +0100

    [gdb/testsuite] Fix gdb.ada/out_of_line_in_inlined.exp for ppc64le
   =20
    On powerpc64le-linux, with test-case gdb.ada/out_of_line_in_inlined.exp=
 I run
    into:
    ...
    (gdb) run ^M
    Starting program: foo_o224_021-all ^M
    ^M
    Breakpoint 1, 0x0000000010002f48 in foo_o224_021.child1.child2 (s=3D...=
) at \
      foo_o224_021.adb:24^M
    24              function Child2 (S : String) return Boolean is -- STOP^M
    (gdb) FAIL: gdb.ada/out_of_line_in_inlined.exp: scenario=3Dall: \
      run to foo_o224_021.child1.child2
    ...
   =20
    The breakpoint is correctly set at the local entry point, and given tha=
t the
    local entry point doesn't correspond to a line number entry, the instru=
ction
    address of the breakpoint is shown.
   =20
    The problem is that test-case doesn't expect the breakpoint address.
   =20
    Fix this by allowing the breakpoint address to occur.
   =20
    Tested on powerpc64le-linux.

Diff:
---
 gdb/testsuite/gdb.ada/out_of_line_in_inlined.exp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gdb/testsuite/gdb.ada/out_of_line_in_inlined.exp b/gdb/testsui=
te/gdb.ada/out_of_line_in_inlined.exp
index 4bdb4decaaf..621b04e179b 100644
--- a/gdb/testsuite/gdb.ada/out_of_line_in_inlined.exp
+++ b/gdb/testsuite/gdb.ada/out_of_line_in_inlined.exp
@@ -34,7 +34,7 @@ foreach_with_prefix scenario {all minimal} {
=20
     gdb_run_cmd
     gdb_test "" \
-	"Breakpoint $decimal, foo_o224_021\\.child1\\.child2 \\(s=3D\\.\\.\\.\\).=
*" \
+	"Breakpoint $decimal, ($hex in )?foo_o224_021\\.child1\\.child2 \\(s=3D\\=
.\\.\\.\\).*" \
 	"run to foo_o224_021.child1.child2"
=20
     set opt_addr_in "($hex in)?"