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.

Description of problem:
I see this on my PPC64 box:

$ ltrace -f -e __libc_start_main -- /bin/true 
[pid 19908] true->__libc_start_main(1, 0xfffd4369c88, 0xfffd4369c98, 0xfffd4369de0breakpoint_on_continue 0x10003cc0 __libc_start_main
 <no return ...>
[pid 19908] --- SIGSEGV (Segmentation fault) ---
[pid 19908] +++ killed by SIGSEGV +++

But when I request tracing of all symbols that are actually called:

$ ltrace -f -e __libc_start_main+exit -- /bin/true 
[pid 19935] true->__libc_start_main(1, 0xffff1c4adf8, 0xffff1c4ae08, 0xffff1c4af50b <unfinished ...>
[pid 19935] true->exit(0, 0xffff1c4adf8, 0xffff1c4ae08, 0xffff1c4af50 <no return ...>
[pid 19935] +++ exited (status 0) +++

I think the problem might be in the part of the PPC64 backend that does unprelinking, but couldn't reproduce this on handcrafted binaries.

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

This is now fixed in upstream as well as in Fedora.  The problem was indeed in unprelinking.

The problem can be reproduced as follows:

$ cat w.c
int main (void) {
  puts("ble");
}
$ gcc w.c 
$ strip a.out 
$ prelink ./a.out 

# This works:
$ ./ltrace  ~/tmp/a.out 
__libc_start_main(1, 0xfffc73b1f78, 0xfffc73b1f88, 0xfffc73b20d0 <unfinished ...>
puts(0x10000740, 0xfffc73b1f78, 0xfffc73b1f88, 0xfffc73b20d0ble
)                                    = 4
+++ exited (status 48) +++

# This doesn't:
$ ltrace -e __libc_start_main ./a.out 
a.out->__libc_start_main(1, 0xfffdf3d3368, 0xfffdf3d3378, 0xfffdf3d34c0 <no return ...>
--- SIGSEGV (Segmentation fault) ---
+++ killed by SIGSEGV +++

Tested with ltrace-0.7.91-4 (reproduced) and ltrace-0.7.91-[56] (works well).

VERIFIED.

This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.