From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7360 invoked by alias); 12 Feb 2014 23:15:18 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 18433 Received: (qmail 2585 invoked from network); 12 Feb 2014 23:15:13 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,HTML_MESSAGE, RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=fO1bD0Me68zoag6oq3GcrGdFjZM3UR2ca2eq8dfEQZ0=; b=kY4PO2HKjF2M2RnxVUJ1wZDiVouDNTg991eJFtP+izaEyAd8eSZPEjnazWJ3XYryem uor0F67I5HCHaKrhemfP25rRQMEvvPgTYk7PAy9o46gr3o2GXpUT1qfQDqOuu4VY7Vrb 2nwlGkCeX4e1Mw2ELdQekxjAvGOOwtAnGKJouT/afl5vAihfmVn0wxV9MTde/qyzFMuw kQXkjlQuhv3Qb+N6ARxadqkhDErFHK3sViUWo4iBtcwHAS8tLI5UR4fnUOlAsy9JzqQG b5CrpT0B9hqToUkMkeJvSJObAgu7TTp3ktuVw7KvEcsYDKaF/9gBHhvyZ0T7RROx+175 zsqQ== X-Gm-Message-State: ALoCoQn19aoocOBEQlP+E6EbGBJPXOAqmdxioWQHC9hmPs/RX/yvtouGbHLqSgthO2yV/CZrm8hy MIME-Version: 1.0 X-Received: by 10.152.19.166 with SMTP id g6mr33240053lae.21.1392246907708; Wed, 12 Feb 2014 15:15:07 -0800 (PST) In-Reply-To: <20140212210909.07a674af@arcor.com> References: <20140212182813.1d48aeaa@hogwart.bsdlocal.net> <20140212210909.07a674af@arcor.com> Date: Wed, 12 Feb 2014 15:15:07 -0800 Message-ID: Subject: Re: history distortion From: Bart Schaefer To: Zsh Users Content-Type: multipart/alternative; boundary=089e01493c0e5fb4ca04f23dbe9d --089e01493c0e5fb4ca04f23dbe9d Content-Type: text/plain; charset=ISO-8859-1 On Wed, Feb 12, 2014 at 12:09 PM, Manfred Lotz wrote: > On Wed, 12 Feb 2014 10:40:45 -0800 > Micah Elliott 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. --089e01493c0e5fb4ca04f23dbe9d--