public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@embecosm.com>
To: gdb-patches@sourceware.org
Subject: [OB PATCH] GDB/testsuite: Fix PARAM_ZUINTEGER reported for PARAM_ZUINTEGER_UNLIMITED
Date: Wed, 17 Aug 2022 23:01:07 +0100 (BST)	[thread overview]
Message-ID: <alpine.DEB.2.20.2208151551350.10833@tpp.orcam.me.uk> (raw)

Correctly report PARAM_ZUINTEGER_UNLIMITED rather than PARAM_ZUINTEGER 
in testing a Python parameter of the PARAM_ZUINTEGER_UNLIMITED type.
---
Hi,

 Committed as obvious.

  Maciej
---
 gdb/testsuite/gdb.python/py-parameter.exp |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

gdb-test-python-param-zuinteger-unlimited.diff
Index: src/gdb/testsuite/gdb.python/py-parameter.exp
===================================================================
--- src.orig/gdb/testsuite/gdb.python/py-parameter.exp
+++ src/gdb/testsuite/gdb.python/py-parameter.exp
@@ -346,9 +346,9 @@ proc_with_prefix test_integer_parameter
 	    gdb_test "python test_param_$kind.value = -1" "RuntimeError: Range exceeded.*"
 	} elseif {$kind == "PARAM_ZUINTEGER_UNLIMITED"} {
 	    gdb_test_no_output "python test_param_$kind.value = -1" \
-		"check that PARAM_ZUINTEGER value can be set to -1"
+		"check that PARAM_ZUINTEGER_UNLIMITED value can be set to -1"
 	    gdb_test "python print(gdb.parameter('test-$kind'))" "-1" \
-		"check that PARAM_ZUINTEGER value is -1 after setting"
+		"check that PARAM_ZUINTEGER_UNLIMITED value is -1 after setting"
 	} else {
 	    error "invalid kind: $kind"
 	}

                 reply	other threads:[~2022-08-17 22:01 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=alpine.DEB.2.20.2208151551350.10833@tpp.orcam.me.uk \
    --to=macro@embecosm.com \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).