Description of problem: Tried to build llvm with -flto. Version-Release number of selected component: dwz-0.8-1.fc18 Additional info: backtrace_rating: 4 cmdline: dwz -h -q -r -m .dwz/mesa-private-llvm-3.1-12.el7.jx1.x86_64 -l 10000000 -L 110000000 ./usr/lib64/mesa-private-llvm/libLLVM-3.1-mesa.so.debug crash_function: remove_import_edges executable: /usr/bin/dwz kernel: 3.6.9-4.jx1.fc18.x86_64 uid: 1000 var_log_messages: Dec 20 11:58:22 ergine abrt[25153]: Saved core dump of pid 25152 (/usr/bin/dwz) to /var/spool/abrt/ccpp-2012-12-20-11:58:21-25152 (240205824 bytes) Truncated backtrace: Thread no. 1 (3 frames) #4 remove_import_edges at dwz.c:5678 #6 create_import_tree at dwz.c:5998 #7 dwz at dwz.c:10976
Created attachment 666820 [details] File: backtrace
Created attachment 666821 [details] File: build_ids
Created attachment 666822 [details] File: cgroup
Created attachment 666823 [details] File: core_backtrace
Created attachment 666824 [details] File: dso_list
Created attachment 666825 [details] File: environ
Created attachment 666826 [details] File: limits
Created attachment 666827 [details] File: maps
Created attachment 666828 [details] File: open_fds
Created attachment 666829 [details] File: proc_pid_status
Can you please attach ./usr/lib64/mesa-private-llvm/libLLVM-3.1-mesa.so.debug before dwz is run on it? E.g. disable dwz through say %global _find_debuginfo_dwz_opts %{nil} or similar in the spec file, build, unpack the so.debug file from the debuginfo rpm? Thanks.
Created attachment 666908 [details] libLLVM-3.1-mesa.so.debug.bz2 As requested.
As suspected, the LTO debug info is very questionable, contains several copies of the same DIEs within the same compilation unit. --- dwz-0.8/dwz.c +++ dwz-0.8/dwz.c @@ -3433,6 +3433,12 @@ die_eq_1 (dw_cu_ref cu1, dw_cu_ref cu2, reft1 = reft2; reft2 = tem; } + if (reft1->die_dup == NULL && reft2->die_dup != NULL) + { + dw_die_ref tem = reft1; + reft1 = reft2; + reft2 = tem; + } } /* If reft1 (die1 or whatever refers to it is already in the hash table) already has a dup, follow to that should fix this, I'll need to run dwz on a larger code base to double check it works correctly though.
Now in dwz-0.9-1.fc{18,19}. Not pushed as an update yet, can you please verify it fixes your build?
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.