Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1132710

Summary: rebase zsh to 4.3.11
Product: Red Hat Enterprise Linux 6 Reporter: Matt Goldman <magoldma>
Component: zshAssignee: Kamil Dudka <kdudka>
Status: CLOSED ERRATA QA Contact: Jan Kepler <jkejda>
Severity: medium Docs Contact:
Priority: high    
Version: 6.7CC: dkutalek, jkejda, jshort, justin.garrison, kdudka, ovasik, salmy
Target Milestone: rcKeywords: Rebase
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: zsh-4.3.11-1.el6 Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
Rebase package(s) to version: zsh-4.3.11 Highlights, important fixes, or notable enhancements: * Parameter expansion has been enhanced to provide the ${NAME:OFFSET} and ${NAME:OFFSET:LENGTH} syntax for substrings and subarrays present in several other shells. * Numeric expansion with braces has been extended so that a step may be given, as in {3..9..2}. * See /usr/share/doc/zsh/NEWS for details.
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-07-22 06:02:11 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Comment 1 Justin Garrison 2014-08-22 15:35:06 UTC
Another bug that I came across with the existing 4.3.10 version of zsh is in command completion. Logging in via ssh with a command completion with an r causes zsh to fail to load with the following error

*** glibc detected *** -zsh: double free or corruption (fasttop): 0x0000000001473db0 ***
*** glibc detected *** -zsh: double free or corruption (fasttop): 0x0000000001473db0 ***
*** glibc detected *** -zsh: double free or corruption (fasttop): 0x0000000001473db0 ***

more info can be found here http://www.zsh.org/mla/workers/2012/msg00688.html

I didn't test with 4.3.11 but the bug does not happen with 5.0.5.

Comment 3 Kamil Dudka 2014-11-12 18:01:18 UTC
(In reply to Justin Garrison from comment #1)
> I didn't test with 4.3.11 but the bug does not happen with 5.0.5.

The above issue is unrelated to this bug.  It seems to be fixed in 5.0.1:

http://sourceforge.net/p/zsh/code/ci/cba5449c

Please open a separate bug with clear steps to reproduce.

Comment 10 errata-xmlrpc 2015-07-22 06:02:11 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-1273.html