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 1116508 - wrong return code from a function
Summary: wrong return code from a function
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ksh
Version: 6.7
Hardware: Unspecified
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Michal Hlavinka
QA Contact: Martin Kyral
URL:
Whiteboard:
Depends On:
Blocks: 1136318
TreeView+ depends on / blocked
 
Reported: 2014-07-05 12:55 UTC by Marcel Kolaja
Modified: 2018-12-06 17:12 UTC (History)
10 users (show)

Fixed In Version: ksh-20120801-21.el6
Doc Type: Bug Fix
Doc Text:
Previously, ksh could skip setting the exit code from the last command of a function. As a result, function could return wrong exit code. The code was updated to make sure exit code from the last command of a function is used and functions now return correct exit code.
Clone Of:
: 1136318 1146507 (view as bug list)
Environment:
Last Closed: 2014-10-14 07:07:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
reproducer (219 bytes, text/plain)
2014-07-05 13:04 UTC, Marcel Kolaja
no flags Details
patch to fix this (677 bytes, patch)
2014-09-01 12:24 UTC, Michal Hlavinka
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:1381 0 normal SHIPPED_LIVE ksh bug fix update 2014-10-14 01:28:24 UTC

Description Marcel Kolaja 2014-07-05 12:55:23 UTC
Description of problem:
Under some circumstances, one gets an incorrect return code from a function.

Version-Release number of selected component (if applicable):
ksh-20120801-10.el6_5.6.x86_64

How reproducible:
always

Steps to Reproduce:
1. run the reproducer (see the attachment)

Actual results:
Res is: 0
Res is: 1

Expected results:
Res is: 1
Res is: 1

Additional info:
N/A

Comment 1 Marcel Kolaja 2014-07-05 13:04:44 UTC
Created attachment 914813 [details]
reproducer

Please, note that function foo() is affected by the bug while the return code of function bar() is correct.

Comment 2 Marcel Kolaja 2014-07-05 13:10:28 UTC
ksh-20100621-19.el6_4.4.x86_64 works correctly, so it's a regression.

Comment 5 Marcel Kolaja 2014-07-06 10:16:18 UTC
The regression is caused by the fix of bug #994251.

Comment 10 Michal Hlavinka 2014-09-01 12:24:18 UTC
Created attachment 933343 [details]
patch to fix this

Comment 18 errata-xmlrpc 2014-10-14 07:07:46 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.

http://rhn.redhat.com/errata/RHBA-2014-1381.html


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