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 802202[details]
Reproducer
Description of problem:
When ltracing a program with vfork, not all of the _exit calls are catched.
Version-Release number of selected component (if applicable):
ltrace-0.5-23.45svn.el6.ppc64
How reproducible: 100%
Steps to Reproduce:
1. run the attached reproducer
-- or --
1. ltrace -f -o ltrace.log ./vfork64
2. cat ltrace.log | grep _exit
Actual results:
There's only one _exit call in the ltrace, although there should be two of them.
Expected results:
There are all of the calls made by traced app.
Additional info:
- This issue happens only when tracing a 64bit application on ppc64. When you build the same app with -m32 option, everything passes well.
- It happens only on ppc64
- When vfork is substituted by fork, everything passes well.
- The call which is lost is the _exit() call of the parent process.
Comment 2RHEL Program Management
2013-10-13 23:07:27 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.
Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
Created attachment 802202 [details] Reproducer Description of problem: When ltracing a program with vfork, not all of the _exit calls are catched. Version-Release number of selected component (if applicable): ltrace-0.5-23.45svn.el6.ppc64 How reproducible: 100% Steps to Reproduce: 1. run the attached reproducer -- or -- 1. ltrace -f -o ltrace.log ./vfork64 2. cat ltrace.log | grep _exit Actual results: There's only one _exit call in the ltrace, although there should be two of them. Expected results: There are all of the calls made by traced app. Additional info: - This issue happens only when tracing a 64bit application on ppc64. When you build the same app with -m32 option, everything passes well. - It happens only on ppc64 - When vfork is substituted by fork, everything passes well. - The call which is lost is the _exit() call of the parent process.