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 1303777 - SAS Works application crashes with Memory Fault
Summary: SAS Works application crashes with Memory Fault
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ksh
Version: 6.7
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Siteshwar Vashisht
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-01 23:41 UTC by bhudlemeyer
Modified: 2017-06-13 08:04 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-06-13 08:04:44 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Script to reproduce memory dump (547 bytes, application/zip)
2016-02-01 23:41 UTC, bhudlemeyer 		no flags Details
View All

Description bhudlemeyer 2016-02-01 23:41:02 UTC 
Created attachment 1120258 [details]
Script to reproduce memory dump

Description of problem:Memory dump error when running SAS works applications on latest patch


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


How reproducible:Run attached scripts

I have completed the root cause for this issue.
I have isolated the problem to an issue that is present within the latest OS patching for RHEL6.  This new bug was triggered in a section of code within my platform middleware.
 
 
PFA a set of two scripts that can be used to induce the Red Hat bug:

·         testcase.ksh
·         testcase_sub.ksh
 
 
To trigger the issue, you only need to copy the two scripts to the same directory and then run testcase.ksh.
 
Here is the output when running the script on one of RHEL6 servers at the earlier patch level:
 
*:/home/mware/test01> ./testcase.ksh
In script #1: -- testcase.ksh
In script #1:    calling testcase_sub.ksh
In script #2: -- testcase_sub.ksh
In script #1:    RC=0
 
And here is the output when running the script on another RHEL6 server with the updated patch level:
 
*:/home/mware/test01> ./testcase.ksh
In script #1: -- testcase.ksh
In script #1:    calling testcase_sub.ksh
In script #2: -- testcase_sub.ksh
./testcase.ksh: line 6: 27982: Memory fault(coredump)
In script #1:    RC=267
 
2.6.32-573.12.1.el6.x86_64 #1 SMP Mon Nov 23 12:55:32 EST 2015 x86_64 x86_64 x86_64 GNU/Linux
 
Note  that the core dump produces the return code value of 267 that the application team was reporting.


Actual results: Memory Fault


Expected results: Successful run


Additional info: Scripts to reproduce issue attached
Comment 2 Michal Hlavinka 2016-02-02 17:34:33 UTC 
What ksh package do you have exactly?
$ rpm -q ksh
thanks
Note You need to log in before you can comment on or make changes to this bug.