From: "Johan Ström" <johan@stromnet.se>
To: Peter Stephenson <p.w.stephenson@ntlworld.com>, zsh-workers@zsh.org
Subject: Re: "crash: free invalid next size (fast)" on completion
Date: Thu, 24 Mar 2022 11:12:05 +0100 [thread overview]
Message-ID: <87c0f1d5-84cb-e459-7009-aff69da3bdb8@stromnet.se> (raw)
In-Reply-To: <785894966.624349.1648115917719@mail2.virginmedia.com>
On 2022-03-24 10:58, Peter Stephenson wrote:
>> On 24 March 2022 at 07:31 Johan Ström <johan@stromnet.se> wrote:
>>> Do other completions crash, or only completions that involve file names?
>> Not sure, will check with some known completion if I see it again
>> (typically have a bunch of terminal open, and at least previously
>> multiple of them seemed to break)
> Could you leave something running with "valgrind zsh" and see if that crashes
> and gives a bit more information?
>
> Like Bart I'm hard pressed to work out what might be going on while it's
> idle, but it does look like the corruption has already happened when you
> come back to it.
>
> pws
Launched one now. Quickly noticed this:
1. Execute ls
2. Use up-arrow, triggers warning:
==2157023== Invalid read of size 32
==2157023== at 0x4B7709D: __wmemcmp_avx2_movbe (in /usr/lib/libc.so.6)
==2157023== by 0x5863FDC: mkundoent (in /usr/lib/zsh/5.8.1/zsh/zle.so)
==2157023== by 0x5865555: handleundo (in /usr/lib/zsh/5.8.1/zsh/zle.so)
==2157023== by 0x58516F1: zlecore (in /usr/lib/zsh/5.8.1/zsh/zle.so)
==2157023== by 0x5852586: zleread (in /usr/lib/zsh/5.8.1/zsh/zle.so)
==2157023== by 0x1738A2: zleentry (in /usr/bin/zsh)
==2157023== by 0x1741AC: ingetc (in /usr/bin/zsh)
==2157023== by 0x166A93: ??? (in /usr/bin/zsh)
==2157023== by 0x1824CE: ??? (in /usr/bin/zsh)
==2157023== by 0x1A6F87: parse_event (in /usr/bin/zsh)
==2157023== by 0x16CC4D: loop (in /usr/bin/zsh)
==2157023== by 0x175A34: zsh_main (in /usr/bin/zsh)
==2157023== Address 0x5c2de50 is 0 bytes inside a block of size 8 alloc'd
==2157023== at 0x484ACD3: realloc (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==2157023== by 0x586404F: setlastline (in /usr/lib/zsh/5.8.1/zsh/zle.so)
==2157023== by 0x5849799: zle_setline (in /usr/lib/zsh/5.8.1/zsh/zle.so)
==2157023== by 0x5849F10: zle_goto_hist (in
/usr/lib/zsh/5.8.1/zsh/zle.so)
==2157023== by 0x5849F5A: uphistory (in /usr/lib/zsh/5.8.1/zsh/zle.so)
==2157023== by 0x5849FDC: uplineorhistory (in
/usr/lib/zsh/5.8.1/zsh/zle.so)
==2157023== by 0x584F265: execzlefunc (in /usr/lib/zsh/5.8.1/zsh/zle.so)
==2157023== by 0x585183B: zlecore (in /usr/lib/zsh/5.8.1/zsh/zle.so)
==2157023== by 0x5852586: zleread (in /usr/lib/zsh/5.8.1/zsh/zle.so)
==2157023== by 0x1738A2: zleentry (in /usr/bin/zsh)
==2157023== by 0x1741AC: ingetc (in /usr/bin/zsh)
==2157023== by 0x166A93: ??? (in /usr/bin/zsh)
==2157023==
Using up/down arrows a bit triggers the same thing again, but after a
few ups/downs it stops. Can reproduce 100% it seems.
Will leave valgrinds running.
next prev parent reply other threads:[~2022-03-24 10:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <df2ea61b-d0ea-ba95-98e0-d0fe84b800d0@stromnet.se>
[not found] ` <CAH+w=7Yn_jyvHiOtpMAmq8rFESM16LgEdzgGx7t0E+c2ctS1fg@mail.gmail.com>
2022-03-24 7:31 ` Johan Ström
2022-03-24 9:58 ` Peter Stephenson
2022-03-24 10:12 ` Johan Ström [this message]
2022-03-24 10:47 ` Peter Stephenson
2022-03-31 17:17 ` Jun. T
2022-03-31 22:07 ` Bart Schaefer
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=87c0f1d5-84cb-e459-7009-aff69da3bdb8@stromnet.se \
--to=johan@stromnet.se \
--cc=p.w.stephenson@ntlworld.com \
--cc=zsh-workers@zsh.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).