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.

Looking at ltrace-0.5-28.45svn.el6.ppc64 testsuite results I see following:

=======
 6.7 S ppc64 # make check RUNTESTFLAGS='--tool_exec=/usr/bin/ltrace hello-vfork.exp'
... stuff deleted ...
Running ./ltrace.main/hello-vfork.exp ...
FAIL: _exit in /root/rpmbuild/BUILD/ltrace-0.5/testsuite/ltrace.main/hello-vfork.ltrace for 1 times ,should be 2
... stuff deleted ...
# of unexpected failures        1
=======

Reproducing manually:

=======
 6.7 S ppc64 # gcc ./ltrace.main/hello-vfork.c  -g  -lm   -o /root/rpmbuild/BUILD/ltrace-0.5/testsuite/ltrace.main/hello-vfork
 6.7 S ppc64 # ltrace -f /root/rpmbuild/BUILD/ltrace-0.5/testsuite/ltrace.main/hello-vfork |& grep '_exit'
[pid 13727] _exit(0 <unfinished ...>
 6.7 S ppc64 # 
=======

For reference on x86_64 the behaviour is:

=======
 6.7 S x86_64 [-] # gcc ./ltrace.main/hello-vfork.c  -g  -lm   -o /root/rpmbuild/BUILD/ltrace-0.5/testsuite/ltrace.main/hello-vfork
 6.7 S x86_64 [-] # ltrace -f /root/rpmbuild/BUILD/ltrace-0.5/testsuite/ltrace.main/hello-vfork |& grep '_exit'
[pid 32413] _exit(0 <unfinished ...>
_exit(0 <unfinished ...>
 6.7 S x86_64 [-] #
=======

Please, review.

This is due to missed return after first call to reentrant library function.  (_exit is reentered before return from it is seen.  That return is of course never seen).  We had this exact problem open as bug 802746, and currently track it for RHEL 6 as 753130.  The patch-set that fixing this would involve is large and untrivial, which is why 753130 was WONFIX'd.

*** This bug has been marked as a duplicate of bug 753130 ***

If bug 753130 is WONTFIX, then the testcase will always fail and QE will always need to waive it. how about disabling the testcase (possibly with a comment) in the testsuite?