public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Carl Love <carll@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] PowerPC fix for gdb.server/sysroot.exp
Date: Fri,  6 May 2022 23:09:09 +0000 (GMT)	[thread overview]
Message-ID: <20220506230909.233833858C53@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=29004660c947a78c348d250e2e0eccb5d8056e29

commit 29004660c947a78c348d250e2e0eccb5d8056e29
Author: Carl Love <cel@us.ibm.com>
Date:   Thu May 5 16:45:18 2022 -0500

    PowerPC fix for gdb.server/sysroot.exp
    
    On PowerPC, the stop in the printf function is of the form:
    
    Breakpoint 2, 0x00007ffff7c6ab08 in printf@@GLIBC_2.17 () from /lib64/libc.so.6
    
    On other architectures the output looks like:
    
    Breakpoint 2, 0x0000007fb7ea29ac in printf () from /lib/aarch64-linux-gnu/libc.so.6
    
    The following patch modifies the printf test by matchine any character
    starting immediately after the printf.  The test now works for PowerPC
    output as well as the output from other architectures.
    
    The test has been run on a Power 10 system and and Intel x86_64 system.

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

diff --git a/gdb/testsuite/gdb.server/sysroot.exp b/gdb/testsuite/gdb.server/sysroot.exp
index a319200e8d2..95679fc0849 100644
--- a/gdb/testsuite/gdb.server/sysroot.exp
+++ b/gdb/testsuite/gdb.server/sysroot.exp
@@ -78,7 +78,7 @@ foreach_with_prefix sysroot { "local" "remote" } {
 
 	# Test that we can stop inside a library.
 	gdb_breakpoint printf
-	gdb_test "continue" "Breakpoint $decimal.* (__)?printf .*" \
+	gdb_test "continue" "Breakpoint $decimal.* (__)?printf.*" \
 	    "continue to printf"
     }
 }


                 reply	other threads:[~2022-05-06 23:09 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=20220506230909.233833858C53@sourceware.org \
    --to=carll@sourceware.org \
    --cc=gdb-cvs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).