Hide Forgot
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.
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.
*** This bug has been marked as a duplicate of bug 802746 ***