From: "Maciej W. Rozycki" <macro@embecosm.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: Simon Sobisch <simonsobisch@web.de>, Tom Tromey <tom@tromey.com>,
gdb-patches@sourceware.org
Subject: Re: [PATCH v6 1/8] GDB/Guile: Don't assert that an integer value is boolean
Date: Fri, 21 Oct 2022 21:54:07 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.2.20.2210212137470.19931@tpp.orcam.me.uk> (raw)
In-Reply-To: <1962a74c-690c-518e-0bfb-1d9fa2876847@polymtl.ca>
On Fri, 21 Oct 2022, Simon Marchi wrote:
> Hmm, I see this failure now:
>
> guile (set-parameter-value! test-PARAM_ZINTEGER-param #:unlimited)^M
> ERROR: In procedure set-parameter-value!:^M
> In procedure gdbscm_set_parameter_value_x: Wrong type argument in position 2 (expecting integer): #:unlimited^M
> Error while executing Scheme code.^M
> (gdb) FAIL: gdb.guile/scm-parameter.exp: kind=PARAM_ZINTEGER: test-PARAM_ZINTEGER-param: guile (set-parameter-value! test-PARAM_ZINTEGER-param #:unlimited)
>
> This is with Guile 3.0, if that matters.
It's not a failure, the "ERROR: ..." message, perhaps confusingly, comes
from GDB under test rather than the DejaGNU test harness and therefore it
doesn't score as a test error or count towards test results. The context
is:
(gdb) PASS: gdb.guile/scm-parameter.exp: kind=PARAM_ZINTEGER: test-PARAM_ZINTEGER-param: PARAM_ZINTEGER parameter value (2)
guile (set-parameter-value! test-PARAM_ZINTEGER-param #:unlimited)
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.
(gdb) PASS: gdb.guile/scm-parameter.exp: kind=PARAM_ZINTEGER: test-PARAM_ZINTEGER-param: guile (set-parameter-value! test-PARAM_ZINTEGER-param #:unlimited)
and the test case requires that message to be there to pass:
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\\."
so there's nothing to worry about. In other words the test case verifies
that a particular error message is printed by GDB when supplied with a
bogus command. Thanks for your meticulousness though!
Maciej
next prev parent reply other threads:[~2022-10-21 22:49 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 22:03 [PATCH v6 0/8] gdb: split array and string limiting options Maciej W. Rozycki
2022-08-17 22:03 ` [PATCH v6 1/8] GDB/Guile: Don't assert that an integer value is boolean Maciej W. Rozycki
2022-10-17 13:43 ` Simon Marchi via Gdb-patches
2022-10-21 7:58 ` Maciej W. Rozycki
2022-10-21 18:44 ` Simon Marchi via Gdb-patches
2022-10-21 20:54 ` Maciej W. Rozycki [this message]
2022-10-22 0:48 ` Simon Marchi via Gdb-patches
2022-08-17 22:03 ` [PATCH v6 2/8] GDB/doc: Document the Guile `#:unlimited' keyword Maciej W. Rozycki
2022-08-18 6:06 ` Eli Zaretskii via Gdb-patches
2022-09-01 10:31 ` Maciej W. Rozycki
2022-08-17 22:04 ` [PATCH v6 3/8] GDB/testsuite: Expand Python integer parameter coverage across all types Maciej W. Rozycki
2022-10-17 13:56 ` Simon Marchi via Gdb-patches
2022-10-21 7:59 ` Maciej W. Rozycki
2022-08-17 22:04 ` [PATCH v6 4/8] GDB/Python: Make `None' stand for `unlimited' in setting integer parameters Maciej W. Rozycki
2022-10-17 14:26 ` Simon Marchi via Gdb-patches
2022-10-21 8:03 ` Maciej W. Rozycki
2022-08-17 22:04 ` [PATCH v6 5/8] GDB/Python: Use None for `var_zuinteger_unlimited' value set to `unlimited' Maciej W. Rozycki
2022-08-18 6:08 ` Eli Zaretskii via Gdb-patches
2022-10-17 15:02 ` Simon Marchi via Gdb-patches
2022-10-29 15:58 ` Maciej W. Rozycki
2022-10-31 13:00 ` Simon Marchi via Gdb-patches
2022-10-31 13:31 ` Maciej W. Rozycki
2022-11-01 12:28 ` Maciej W. Rozycki
2022-10-26 11:58 ` Luis Machado via Gdb-patches
2022-10-29 13:52 ` Maciej W. Rozycki
2022-10-31 8:14 ` Luis Machado via Gdb-patches
2022-10-31 12:37 ` Luis Machado via Gdb-patches
2022-10-31 13:08 ` Maciej W. Rozycki
2022-10-31 13:14 ` Luis Machado via Gdb-patches
2022-10-31 14:05 ` Maciej W. Rozycki
2022-08-17 22:04 ` [PATCH v6 6/8] GDB: Allow arbitrary keywords in integer set commands Maciej W. Rozycki
2022-08-17 22:05 ` [PATCH v6 7/8] GDB: Add a character string limiting option Maciej W. Rozycki
2022-08-17 22:05 ` [PATCH v6 8/8] GDB/testsuite: Expand for character string limiting options Maciej W. Rozycki
2022-08-18 0:07 ` [PATCH v6.1 " Maciej W. Rozycki
2022-09-01 10:32 ` [PING][PATCH v6 0/8] gdb: split array and " Maciej W. Rozycki
2022-09-08 9:37 ` [PING^2][PATCH " Maciej W. Rozycki
2022-09-14 17:43 ` [PING^3][PATCH " Maciej W. Rozycki
2022-09-22 22:07 ` [PING^4][PATCH " Maciej W. Rozycki
2022-09-29 7:09 ` [PING^5][PATCH " Maciej W. Rozycki
2022-09-29 7:12 ` Simon Sobisch via Gdb-patches
2022-10-06 15:46 ` [PING^6][PATCH " Maciej W. Rozycki
2022-10-12 21:19 ` [PING^7][PATCH " Maciej W. Rozycki
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.2210212137470.19931@tpp.orcam.me.uk \
--to=macro@embecosm.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
--cc=simonsobisch@web.de \
--cc=tom@tromey.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