public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Tom de Vries <vries@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] [gdb/testsuite] Fix gdb.arch/i386-mpx.exp
Date: Mon, 18 Jul 2022 03:54:17 +0000 (GMT)	[thread overview]
Message-ID: <20220718035417.88F013858CDA@sourceware.org> (raw)

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

commit 68a5118c481da16f81874a92f4daaab4dcdc5d89
Author: Tom de Vries <tdevries@suse.de>
Date:   Mon Jul 18 05:54:14 2022 +0200

    [gdb/testsuite] Fix gdb.arch/i386-mpx.exp
    
    Since commit c4a3dbaf113 ("Expose current 'print' settings to Python") we
    have:
    ...
    (gdb) print /x $bnd0 = {0x10, 0x20}^M
    $22 = {lbound = 0x10, ubound = 0x20} : size 0x11^M
    (gdb) FAIL: gdb.arch/i386-mpx.exp: verify size for bnd0
    ...
    
    The regexp in the test-case expects "size 17".
    
    Fix this by updating the regexp.
    
    Tested on x86_64-linux.

Diff:
---
 gdb/testsuite/gdb.arch/i386-mpx.exp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gdb/testsuite/gdb.arch/i386-mpx.exp b/gdb/testsuite/gdb.arch/i386-mpx.exp
index 336c0464833..0de86ba0237 100644
--- a/gdb/testsuite/gdb.arch/i386-mpx.exp
+++ b/gdb/testsuite/gdb.arch/i386-mpx.exp
@@ -132,5 +132,5 @@ after a failure on allocating an entry"
 # Going to test the python extension for lenght.
 if { [skip_python_tests] } { continue }
 # Verify if size is right
-set test_string ".*\\\: size 17.*"
+set test_string ".*\\\: size 0x11.*"
 gdb_test "print /x \$bnd0 = {0x10, 0x20}" "$test_string" "verify size for bnd0"


                 reply	other threads:[~2022-07-18  3:54 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=20220718035417.88F013858CDA@sourceware.org \
    --to=vries@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).