Created attachment 698013 [details] core file, xz-compressed, produced by prelink Description of problem: A prelink run, initiated by anacron, terminated prematurely with a core dump. This happened when 'yum update' transaction was running but it was still in an "update" phase and not "cleanup" and comparing logs, and times, does not give anything "obvious". Prelink log looks like this: .....Laying out 1059 libraries in virtual address space 0000003000000000-0000004000000000 Random base 0x0000003580200000 Assigned virtual address space slots for 64-bit x86-64 ELF libraries: /lib64/ld-linux-x86-64.so.2 0000003580200000-0000003580422208 ..... /lib64/libaudgui.so.1 000000358a200000-000000358a417cc8 /lib64/libmikmod.so.3 0000003581600000-0000003581855280 Prelink failed with return value 134 After installing prelink-debuginfo gdb gives this: Core was generated by `/usr/sbin/prelink -av -mR'. Program terminated with signal 6, Aborted. #0 0x000000000043ddfb in raise () (gdb) where #0 0x000000000043ddfb in raise () #1 0x0000000000456288 in abort () #2 0x00000000004112d7 in layout_libs () at layout.c:578 #3 0x000000000040303b in main (argc=3, argv=0x7fff59838c48) at main.c:483 (gdb) f 2 #2 0x00000000004112d7 in layout_libs () at layout.c:578 578 abort (); (gdb) l 573 struct prelink_entry *last = list; 574 base = 0; 575 for (e = list; e; last = e, e = e->next) 576 { 577 if (e->base < base) 578 abort (); 579 base = e->base; 580 if ((e == list && e->prev->next != NULL) 581 || (e != list && e->prev->next != e)) 582 abort (); Values for 'e' and 'list' are "optimized out". Version-Release number of selected component (if applicable): prelink-0.4.6-8.fc19.x86_64 How reproducible: I do not recall seeing that before. Additional info: Running later '/usr/sbin/prelink -av -mR' finished without any incidents. Yes, I realize that 'abort ()' was called because 'if (e->base < base)' triggered.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.