From: "Maciej W. Rozycki" <macro@embecosm.com>
To: Simon Marchi <simon.marchi@efficios.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/testsuite: fix gdb.guile/scm-parameter.exp "wrong type argument" test pattern
Date: Tue, 25 Oct 2022 00:22:04 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.2.20.2210250014471.19931@tpp.orcam.me.uk> (raw)
In-Reply-To: <20221024164338.1762303-1-simon.marchi@efficios.com>
On Mon, 24 Oct 2022, Simon Marchi wrote:
> 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.
FTR I'm still looking into it and like you I have hesitated to just paper
the issue over by allowing both outputs without first understanding what
is really going on here. I cannot rule out a distribution-specific patch
causing a discrepancy here, but I feel like tracking it down.
NB guile 2.0.13 here, reporting as:
guile (GNU Guile) 2.0.13
Packaged by Debian (2.0.13-deb+1-5.4)
(and it seems like I have said version consistently throughout my relevant
development machines except for different "-deb+..." suffixes). It must
have had long distribution maintenance history.
Maciej
next prev parent reply other threads:[~2022-10-24 23:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 16:43 Simon Marchi
2022-10-24 23:22 ` Maciej W. Rozycki [this message]
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=alpine.DEB.2.20.2210250014471.19931@tpp.orcam.me.uk \
--to=macro@embecosm.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@efficios.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).