From: Simon Marchi <simon.marchi@efficios.com>
To: gdb-patches@sourceware.org
Cc: "Maciej W . Rozycki" <macro@embecosm.com>,
Simon Marchi <simon.marchi@efficios.com>
Subject: [PATCH] gdb/testsuite: fix gdb.guile/scm-parameter.exp "wrong type argument" test pattern
Date: Mon, 24 Oct 2022 12:43:38 -0400 [thread overview]
Message-ID: <20221024164338.1762303-1-simon.marchi@efficios.com> (raw)
Since commit 90319cefe3 ("GDB/Guile: Don't assert that an integer value
is boolean"), I see:
FAIL: gdb.guile/scm-parameter.exp: kind=PARAM_ZINTEGER: test-PARAM_ZINTEGER-param: guile (set-parameter-value! test-PARAM_ZINTEGER-param #:unlimited)
FAIL: gdb.guile/scm-parameter.exp: kind=PARAM_ZUINTEGER: test-PARAM_ZUINTEGER-param: guile (set-parameter-value! test-PARAM_ZUINTEGER-param #:unlimited)
This comes from the fact that GDB outputs this:
ERROR: In procedure set-parameter-value!:
In procedure gdbscm_set_parameter_value_x: Wrong type argument in position 2 (expecting integer): #:unlimited
Error while executing Scheme code.
while the test expects an additional "ERROR:" on the second line,
something like this:
ERROR: In procedure set-parameter-value!:
ERROR: In procedure gdbscm_set_parameter_value_x: Wrong type argument in position 2 (expecting integer): #:unlimited
Error while executing Scheme code.
The patch below fixes the test for me.
I believe that the first two lines are output by Guile itself, in the
SCM_ASSERT_TYPE macro. I tried on different systems, different Guile
versions (2.0, 2.2 and 3.0) and I always get the former output, never
the output the test expects. I presume the patch below isn't right, as
there is surely some systems that do print the latter output, otherwise
Maciej (the original author) would have noticed it. I presume we'll
need to accept both outputs. But I'd like we if could clarify when we
get which.
Change-Id: I9dc45e7492a4f08340cad974610242ed689de959
---
gdb/testsuite/gdb.guile/scm-parameter.exp | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/gdb/testsuite/gdb.guile/scm-parameter.exp b/gdb/testsuite/gdb.guile/scm-parameter.exp
index b9f2d825211..5d72da935bc 100644
--- a/gdb/testsuite/gdb.guile/scm-parameter.exp
+++ b/gdb/testsuite/gdb.guile/scm-parameter.exp
@@ -183,10 +183,10 @@ foreach_with_prefix kind {
"end"
set param_integer_error \
- "ERROR: In procedure set-parameter-value!:\r\nERROR: In procedure\
- gdbscm_set_parameter_value_x: Wrong type argument in position 2\
- \\(expecting integer\\): #:unlimited\r\nError while executing Scheme\
- code\\."
+ [multi_line \
+ "ERROR: In procedure set-parameter-value!:" \
+ "In procedure gdbscm_set_parameter_value_x: Wrong type argument in position 2 \\(expecting integer\\): #:unlimited" \
+ "Error while executing Scheme code\\."]
set param_minus_one_error "integer -1 out of range"
set param_minus_two_range "integer -2 out of range"
set param_minus_two_unlimited "only -1 is allowed to set as unlimited"
--
2.37.3
next reply other threads:[~2022-10-24 16:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 16:43 Simon Marchi [this message]
2022-10-24 23:22 ` Maciej W. Rozycki
2022-10-25 1:08 ` Simon Marchi
2022-10-26 7:15 ` Tom de Vries
2022-10-26 15:31 ` Simon Marchi
2022-10-29 13:56 ` [OB PATCH] gdb/testsuite: Wrap `param_integer_error' in gdb.guile/scm-parameter.exp Maciej W. Rozycki
2022-10-31 12:57 ` Simon Marchi
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=20221024164338.1762303-1-simon.marchi@efficios.com \
--to=simon.marchi@efficios.com \
--cc=gdb-patches@sourceware.org \
--cc=macro@embecosm.com \
/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).