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.
Created attachment 1127918[details]
comsub-eof.sh
In rhel5, the test case would work and not produce any
warnings. In rhel6 or newer it fails.
Some users have scripts that rely on this behavior, that
did work on previous versions of bash, and works with old
and current versions of ksh.
This is an inconsistency of $() versus ``, as with back
tildes it works with current bash version.
The attached test case is bash/tests/comsub-eof4.sub and
bash/tests/comsub-eof5.sub that explicitly test for the
failure. *But* in bash/parse.y there is also a comment
about supporting this feature:
"""
/* XXX -- possibly allow here doc to be delimited by ending right
paren. */
if ((tflags & LEX_INHEREDOC) && ch == close && count == 1)
{
int tind;
/*itrace("parse_comsub: in here doc, ch == close, retind - firstind = %d hdlen = %d retind = %d", retind-lex_firstind, hdlen, retind);*/
tind = lex_firstind;
while ((tflags & LEX_STRIPDOC) && ret[tind] == '\t')
"""
Created attachment 1127922[details]
bash-4.2-heredoc-paren-delim.patch
This patch, built and tested on rhel7 corrects the issue.
Note that while the patch should be fully functional, and
tests quite a lot of the parser state, it should be possible
to write a simpler one, but I preferred to make a chain of
tests to avoid it being triggered on non matching conditions.
Created attachment 1127918 [details] comsub-eof.sh In rhel5, the test case would work and not produce any warnings. In rhel6 or newer it fails. Some users have scripts that rely on this behavior, that did work on previous versions of bash, and works with old and current versions of ksh. This is an inconsistency of $() versus ``, as with back tildes it works with current bash version. The attached test case is bash/tests/comsub-eof4.sub and bash/tests/comsub-eof5.sub that explicitly test for the failure. *But* in bash/parse.y there is also a comment about supporting this feature: """ /* XXX -- possibly allow here doc to be delimited by ending right paren. */ if ((tflags & LEX_INHEREDOC) && ch == close && count == 1) { int tind; /*itrace("parse_comsub: in here doc, ch == close, retind - firstind = %d hdlen = %d retind = %d", retind-lex_firstind, hdlen, retind);*/ tind = lex_firstind; while ((tflags & LEX_STRIPDOC) && ret[tind] == '\t') """