From: "Johan Ström" <email@example.com>
To: Bart Schaefer <firstname.lastname@example.org>
Cc: Zsh hackers list <email@example.com>
Subject: Re: 5.9 core dumps under zleentry->zleread->zlecore
Date: Thu, 2 Jun 2022 11:25:23 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
On 2022-06-02 09:31, Bart Schaefer wrote:
> The end of the previous thread was that you had valgrind running, but
> we never heard any more from you after one report that was considered
> a false positive.
I think I submitted at least one valgrind post of initial warnings,
which was probably bogus, but then I didn't really manage to reproduce
it unfortunately, and it kind of got forgotten.
> We're going to need some more info on this, I fear -- would it at
> least be possible for you to configure --enable-zsh-debug and
> recompile, so that you get a stack trace with line numbers?
now and added --enable-zsh-debug.
Running with that now, will report back if it crashes again.
During make check one failure occurred though, had to skip 'make check':
Testing multibyte with locale en_US.UTF-8
--- /tmp/zsh.ztst.4900/ztst.err 2022-06-02 11:12:41.488316802 +0200
+++ /tmp/zsh.ztst.4900/ztst.terr 2022-06-02 11:12:41.488316802 +0200
@@ -1 +1 @@
-./test_bad_param:1: command not found: $\M-i#
+./test_bad_param:1: invalid or incomplete multibyte or wide character:
Test ./D07multibyte.ztst failed: error output differs from expected as
shown above for:
# The following doesn't necessarily need UTF-8, but this gives
# us the full effect --- if we parse this wrongly the \xe9
# in combination with the tokenized input afterwards looks like a
# valid UTF-8 character. But it isn't.
print $'$\xe9#``' >test_bad_param
Was testing: Invalid parameter name with following tokenized input
./D07multibyte.ztst: test failed.
next prev parent reply other threads:[~2022-06-02 9:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 7:11 Johan Ström
2022-06-02 7:31 ` Bart Schaefer
2022-06-02 9:25 ` Johan Ström [this message]
2022-06-03 7:14 ` Jun T
2022-06-03 7:19 ` Johan Ström
2022-06-03 9:53 ` Jun T
2022-06-03 10:02 ` Johan Ström
2022-06-04 3:32 ` Bart Schaefer
2022-06-04 7:39 ` Johan Ström
2022-06-04 20:06 ` Bart Schaefer
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.
Code repositories for project(s) associated with this public inbox
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 NNTP newsgroup(s).