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 616771 - set -x can crash mksh
Summary: set -x can crash mksh
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: mksh
Version: 6.1
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Michal Hlavinka
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On:
Blocks: 667075
TreeView+ depends on / blocked
 
Reported: 2010-07-21 12:00 UTC by Michal Hlavinka
Modified: 2011-05-19 13:13 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
mksh was not handling trace output correctly. When tracing was enabled and there was long string to be reported, mksh sometimes crashed. Updated mksh version has improved long trace output handling. Long trace output is now successfully printed without mksh crash
Clone Of:
: 667075 (view as bug list)
Environment:
Last Closed: 2011-05-19 13:13:44 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0580 0 normal SHIPPED_LIVE mksh bug fix and enhancement update 2011-05-18 17:56:53 UTC

Description Michal Hlavinka 2010-07-21 12:00:55 UTC 
Description of problem:
set -x can sometimes crash mksh 

Version-Release number of selected component (if applicable):


How reproducible:
always

Steps to Reproduce:
mksh -x -c 'exec 4>aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa'
  
Actual results:
crash

Expected results:
no crash

Additional info:
exists in pdksh too, bug was there last 11 years (at least)

we need this:
https://www.mirbsd.org/cvs.cgi/src/bin/mksh/sh.h.diff?r2=1.399&r1=1.398&f=u
https://www.mirbsd.org/cvs.cgi/src/bin/mksh/shf.c.diff?r2=1.36&r1=1.35&f=u
Comment 3 Florian Nadge 2011-03-01 11:06:07 UTC 
Florian Nadge 2011-01-19 10:40:58 EST

Please be so kind and add a few key words to the technical note of this
bugzilla entry using the following structure:

Cause:

Consequence:

Fix:

Result:


For details, see:
https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes

Thanks

[reply] [-]
Private
Comment 22
Comment 4 Florian Nadge 2011-03-01 11:06:07 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Cause
    What actions or circumstances cause this bug to present.
Consequence
    What happens when the bug presents.
Fix
    What was done to fix the bug.
Result
    What now happens when the actions or circumstances above occur.
    Note: this is not the same as the bug doesn’t present anymore.
Comment 5 Michal Hlavinka 2011-03-01 13:38:20 UTC 
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1,9 +1 @@
-Cause
+mksh was not handling trace output correctly. When tracing was enabled and there was long string to be reported, mksh sometimes crashed. Updated mksh version has improved long trace output handling. Long trace output is now successfully printed without mksh crash-    What actions or circumstances cause this bug to present.
-Consequence
-    What happens when the bug presents.
-Fix
-    What was done to fix the bug.
-Result
-    What now happens when the actions or circumstances above occur.
-    Note: this is not the same as the bug doesn’t present anymore.
Comment 7 errata-xmlrpc 2011-05-19 13:13:44 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0580.html
Note You need to log in before you can comment on or make changes to this bug.