Bug 1398740 - zsh error "Bad substitution
Summary: zsh error "Bad substitution
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: zsh
Version: 7.2
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Kamil Dudka
QA Contact: Jan Kepler
URL:
Whiteboard:
Depends On:
Blocks: 1298243 1393867
TreeView+ depends on / blocked
 
Reported: 2016-11-25 18:00 UTC by Paulo Andrade
Modified: 2020-09-10 09:59 UTC (History)
4 users (show)

Fixed In Version: zsh-5.0.2-28.el7
Doc Type: If docs needed, set a value
Doc Text:
NEEDLESS TO DOCUMENT
Clone Of:
Environment:
Last Closed: 2017-08-01 20:38:39 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:1955 0 normal SHIPPED_LIVE zsh bug fix update 2017-08-01 18:30:06 UTC

Description Paulo Andrade 2016-11-25 18:00:25 UTC
Simple reproducer (does not need to run in ksh emulation mode):

"""
$ cat toto.sh
#!/usr/bin/ksh

typeset -A person
person[firstname]="frank"
person[lastname]="jones"

echo "person: ${person[firstname]} ${person[lastname]}"
"""

if run:

$ zsh -n toto.sh
toto.sh:7: bad substitution

Bisecting zsh upstream, the problem is corrected in commit
https://sourceforge.net/p/zsh/code/ci/a0862f6381979b165e864e9c5b97d12432d35d48/

Comment 2 Kamil Dudka 2016-11-28 10:51:32 UTC
Thank you for identifying the upstream commit with the fix for this bug!

I can confirm that it resolves the issue and it should be safe to backport.

Comment 8 Jakub Heger 2017-02-21 15:48:31 UTC
Verified.
Reproduced on version: zsh-5.0.2-25.el7.x86_64
Verified on version: zsh-5.0.2-28.el7

Old output: ./repr.sh:7: bad substitution
New output: <empty>

TCMS case run:
https://tcms.engineering.redhat.com/run/304641/#caserun_15218383

Comment 10 errata-xmlrpc 2017-08-01 20:38:39 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://access.redhat.com/errata/RHBA-2017:1955


Note You need to log in before you can comment on or make changes to this bug.