Description of problem: This fnctionality introduced in RHEL 7.2 does not work on ppc64 and ppc64le due to error detected by elfutils in the backtrace. If compiled with the following patch: diff --git a/satyr.c b/satyr.c index 44bf869..117c209 100644 --- a/satyr.c +++ b/satyr.c @@ -283,6 +283,7 @@ debug_duphash(int argc, char **argv) static void debug_unwind_from_hook(int argc, char **argv) { + stderr = fopen("/tmp/satyr-stderr", "w"); if (argc != 3) { fprintf(stderr, "Wrong number of arguments.\n"); satyr saves the error message (otherwise if just fails silently): # cat /tmp/satyr-stderr Unwind failed: dwfl_getthread_frames failed: No DWARF information found eu-stack shows the same problem: # eu-stack --core=core.28115 -e /usr/bin/will_segfault PID 28115 - core TID 28115: #0 0x0000000010000a04 crash #1 0x0000000010000ab8 varargs #2 0x0000000010000b00 f #3 0x0000000010000b50 callback #4 0x00003fffa5be0980 call_me_back #5 0x0000000010000bb0 recursive #6 0x0000000010000b90 recursive #7 0x0000000010000b90 recursive #8 0x00000000100007b8 main #9 0x00003fffa5a25e6c generic_start_main.isra.0 eu-stack: dwfl_thread_getframes tid 28115 at 0x3fffa5a25e6b in libc.so.6: No DWARF information found The issue lies in the extra frame generated on the architectures in question after the main frame. However, satyr shall at least save what's been already unwinded and not fail silently. Version-Release number of selected component (if applicable): satyr-0.13-12.el7 How reproducible: Always Steps to Reproduce: 1. |/usr/bin/satyr debug unwind-from-hook -vvv %e %p %s' > /proc/sys/kernel/core_pattern 2. sleep 3000 & 3. kill -11 $! Actual results: No stacktrace generated Expected results: Stacktrace generated Additional info:
We will very likely have no resources to fix this bug during Red Hat Enterprise Linux 7 time life. Moving to upstream. If you insisted on fixing in Red Hat Enterprise Linux 7 please open a support ticket.
This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle. Changing version to 33.
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.