From: Manfred Lotz <manfred.lotz@arcor.de>
To: zsh-users@zsh.org
Subject: Re: history distortion
Date: Thu, 13 Feb 2014 05:37:30 +0100 [thread overview]
Message-ID: <20140213053730.06e6df12@arcor.com> (raw)
In-Reply-To: <CAH+w=7aST52d+5OoMTkhmd0kOSpeziKiNQhRft67aA1Y0HcKeQ@mail.gmail.com>
On Wed, 12 Feb 2014 15:15:07 -0800
Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Wed, Feb 12, 2014 at 12:09 PM, Manfred Lotz
> <manfred.lotz@arcor.de>wrote:
>
> > On Wed, 12 Feb 2014 10:40:45 -0800
> > Micah Elliott <mde@micahelliott.com> wrote:
> >
> > > I was seeing this too, up to a couple months ago (apologies for
> > > being too lazy to report). I'm on an Arch rolling release and
> > > it's fixed now, so not sure if the problem was specific to the
> > > zsh version or something else on the system that updated (saw an
> > > earlier thread about a memcmp bug, I think).
> >
> > I tried out omitting hist_reduce_blanks and it seems that the
> > problem doesn't show up.
> >
>
> Yes, in zsh prior to 5.0.3 part of the hist_reduce_blanks
> implementation was using memcpy on overlapping regions of the command
> line. memcpy is allowed to optimize the copy by moving several bytes
> at a time, copying right-to-left instead of left-to-right, etc., so
> is not safe for overlaps. The release of a new shared C library that
> changed the memcpy implementation to such an optimized one could
> break existing zsh installs when they started dynamically linking
> against the new library.
>
> This is very likely what happened to you. The distro you are using
> will need to either update zsh or back out the C library
> incompatibility.
>
Good to know that my observation was right. For the time being I leave
out hist_reduce_blanks till the Fedora zsh package has been updated.
Thanks.
--
Manfred
prev parent reply other threads:[~2014-02-13 4:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 17:28 Manfred Lotz
2014-02-12 18:40 ` Micah Elliott
2014-02-12 20:09 ` Manfred Lotz
2014-02-12 23:15 ` Bart Schaefer
2014-02-13 4:37 ` Manfred Lotz [this message]
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=20140213053730.06e6df12@arcor.com \
--to=manfred.lotz@arcor.de \
--cc=zsh-users@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).