Description of problem: I ran the gdb test suite in "dwz -m" mode. In this mode it copies each produced executable and runs "dwz -m" on both the original and the copy. Version-Release number of selected component: dwz-0.8-1.fc18 Additional info: reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: dwz -m /home/tromey/gnu/baseline-gdb/build/gdb/testsuite/gdb.dwarf2/dw2-restrict.dwz /home/tromey/gnu/baseline-gdb/build/gdb/testsuite/gdb.dwarf2/dw2-restrict /home/tromey/gnu/baseline-gdb/build/gdb/testsuite/gdb.dwarf2/dw2-restrict.alt crash_function: write_die executable: /usr/bin/dwz kernel: 3.9.9-201.fc18.x86_64 runlevel: N 5 uid: 1000 Truncated backtrace: Thread no. 1 (4 frames) #4 write_die at dwz.c:9059 #5 write_info at dwz.c:9295 #6 write_multifile at dwz.c:10743 #8 dwz at dwz.c:11115
Created attachment 784025 [details] File: backtrace
Created attachment 784026 [details] File: cgroup
Created attachment 784027 [details] File: core_backtrace
Created attachment 784028 [details] File: dso_list
Created attachment 784029 [details] File: environ
Created attachment 784030 [details] File: limits
Created attachment 784031 [details] File: maps
Created attachment 784032 [details] File: open_fds
Created attachment 784033 [details] File: proc_pid_status
Created attachment 784034 [details] File: var_log_messages
Can you please attach the files on which dwz crashed? Thanks.
Created attachment 786565 [details] the executable I can reproduce the crash with: dwz -m Out dw2-restrict dw2-restrict It is odd to pass in the same file twice, I suppose, but that is how we get any testing of this feature at all in gdb. The executable is about all we have available when testing...
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.
Fixed at https://sourceware.org/bugzilla/show_bug.cgi?id=24171