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 1212775 - case in a for loop inside subshell causes syntax error
Summary: case in a for loop inside subshell causes syntax error
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: bash
Version: 7.1
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Ondrej Oprala
QA Contact: Martin Kyral
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-04-17 09:56 UTC by Jiri Jaburek
Modified: 2015-11-19 04:39 UTC (History)
4 users (show)

Fixed In Version: bash-4.2.46-17.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1240994 1241013 1241014 1241021 1241023 1241024 1245094 1552013 (view as bug list)
Environment:
Last Closed: 2015-11-19 04:39:50 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:2144 0 normal SHIPPED_LIVE bash bug fix update 2015-11-19 08:06:34 UTC

Description Jiri Jaburek 2015-04-17 09:56:01 UTC
Description of problem:

# this works
$ x=$(for i in test; do echo $i; done)
$ echo $x
test

# this too, works
$ i=test
$ x=$(case $i in test) echo test;; esac)
$ echo $x
test

# this does not
$ x=$(for i in test; do case $i in test) echo test;; esac; done)
-bash: syntax error near unexpected token `;;'

# however removing the output-into-variable makes it work
$ (for i in test; do case $i in test) echo test;; esac; done)
test


Version-Release number of selected component (if applicable):
bash-4.2.46-12.el7

How reproducible:
always

Actual results:
expression fails on syntax error

Expected results:
the subshell output is assigned to a variable

Additional info:
This *works* on my bash-4.3.30-2.fc21, so there might have been an upstream fix.

Comment 1 Ondrej Oprala 2015-04-18 13:36:45 UTC
Hi Jiri,
Yes, this was fixed in 4.3. I have yet to look at the size of the change.

Meanwhile, the more verbose way of writing a case statement still seems to work:
x=$(for i in test; do case $i in (test) echo test;; esac; done)
#                                ^^

Comment 3 Ondrej Vasik 2015-05-18 13:04:16 UTC
Yes, he does.

Comment 8 errata-xmlrpc 2015-11-19 04:39:50 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-2144.html


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