Description of problem: report_uReport exit with error when processing a coredump generated by a statically linked executable, being position independant (PIE) or not. Steps to Reproduce: $ cat > abort.c #include <stdlib.h> int main(void) { abort(); return 1; } $ gcc -Og -g -static abort.c -o abort $ gcc -Og -g -static-pie abort.c -o abort-pie $ file ./abort ./abort: ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), statically linked, for GNU/Linux 3.2.0, BuildID[sha1]=63a6e28516a8fa847aec086bb382025cc258cf7a, with debug_info, not stripped, too many notes (256) $ file ./abort-pie ./abort-pie: ELF 64-bit LSB pie executable, x86-64, version 1 (GNU/Linux), dynamically linked, for GNU/Linux 3.2.0, BuildID[sha1]=7f798824b25ca3a89ce016213c4755c43719fc36, with debug_info, not stripped, too many notes (256) $ ldd ./abort not a dynamic executable $ ldd ./abort-pie statically linked $ ./abort Aborted (core dumped) $ abrt-cli list | head id 9957feee1593fd6dae07a0056670683887b475ec reason: abort killed by SIGABRT time: Wed May 29 16:58:55 2019 cmdline: ./abort uid: 1000 (ydroneaud) count: 2 Directory: /var/spool/abrt/ccpp-2019-05-29-16:58:55.167755-24203 $ abrt-cli report 9957feee1593fd6dae07a0056670683887b475ec Error: No segments found in coredump './coredump' ('report_uReport' exited with 1) $ ./abort-pie Aborted (core dumped) $ abrt-cli list | head id f71fbd7742601f9609a0035115494a8920712bb9 reason: abort-pie killed by SIGABRT time: Wed May 29 16:48:57 2019 cmdline: ./abort-pie uid: 1000 (ydroneaud) count: 4 Directory: /var/spool/abrt/ccpp-2019-05-29-16:48:57.169956-23666 $ abrt-cli report f71fbd7742601f9609a0035115494a8920712bb9 Error: No segments found in coredump './coredump' ('report_uReport' exited with 1) Actual results: No report can be sent to bugzilla through ABRT. Expected results: Being able to report a crash in ldconfig (see bug #1609351). Comments: coredumpctl is able to process the coredump and print a backtrace: $ LD_LIBRARY_PATH=/foo/'$LIB' ldconfig Segmentation fault (core dumped) $ coredumpctl info ldconfig [...] Command Line: ldconfig Executable: /usr/sbin/ldconfig [...] Storage: /var/lib/systemd/coredump/core.ldconfig.1000.74610284772e4ba9aa8e774d6c734287.23026.1559140510000000.lz4 Message: Process 23026 (ldconfig) of user 1000 dumped core. Stack trace of thread 23026: #0 0x00007f3e6dfa20fb expand_dynamic_string_token (/usr/sbin/ldconfig) #1 0x00007f3e6dfa2232 fillin_rpath (/usr/sbin/ldconfig) #2 0x00007f3e6dfa28ee _dl_init_paths (/usr/sbin/ldconfig) #3 0x00007f3e6df75d2f _dl_non_dynamic_init (/usr/sbin/ldconfig) #4 0x00007f3e6df77cf4 __libc_init_first (/usr/sbin/ldconfig) #5 0x00007f3e6df17929 __libc_start_main (/usr/sbin/ldconfig) #6 0x00007f3e6df1177e _start (/usr/sbin/ldconfig) But abrt-cli cannot report it: $ abrt-cli list | head id 5e3f3a400252105240c99627b39055808022bd3b reason: ldconfig killed by SIGSEGV time: Wed May 29 16:35:10 2019 cmdline: ldconfig package: glibc-2.29-12.fc30 uid: 1000 (ydroneaud) count: 3 Directory: /var/spool/abrt/ccpp-2019-05-29-16:35:10.920157-23026 $ abrt-cli report 5e3f3a400252105240c99627b39055808022bd3b Error: No segments found in coredump './coredump' ('report_uReport' exited with 1)
I've traced the origin of the error message in libsatyr.so.3.0.0. More specificaly in lib/core_unwind.c:open_coredump(): if (!head) { if (error_msg && !*error_msg) set_error("No segments found in coredump '%s'", elf_file); goto fail_dwfl; } See https://github.com/abrt/satyr/blob/44f748634560846a440ff46e9eb32e884a118a2e/lib/core_unwind.c#L203
This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. 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 '30'. 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 30 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.
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. 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 '31'. 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 31 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.
Still applicable with Fedora 32
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.