Description of problem: Honestly, I do not know what happened or how it can be reproduced. I was just in the terminal installing some softwares, like mariadb, php and apache and postgresql and then i left. came back and i got this error. Version-Release number of selected component: binutils-2.23.51.0.1-3.fc18 Additional info: backtrace_rating: 4 cmdline: /usr/bin/ld --build-id --no-add-needed --eh-frame-hdr --hash-style=gnu -m elf_x86_64 -export-dynamic -dynamic-linker /lib64/ld-linux-x86-64.so.2 -o conftest /usr/lib/gcc/x86_64-redhat-linux/4.7.2/../../../../lib64/crt1.o /usr/lib/gcc/x86_64-redhat-linux/4.7.2/../../../../lib64/crti.o /usr/lib/gcc/x86_64-redhat-linux/4.7.2/crtbegin.o -L. -L../.. -L/home/sidney/.rvm/usr/lib -L. -L/home/sidney/.rvm/usr/lib -L/home/sidney/.rvm/rubies/ruby-2.0.0-p0/lib -L/usr/lib/gcc/x86_64-redhat-linux/4.7.2 -L/usr/lib/gcc/x86_64-redhat-linux/4.7.2/../../../../lib64 -L/lib/../lib64 -L/usr/lib/../lib64 -L/usr/lib/gcc/x86_64-redhat-linux/4.7.2/../../.. /tmp/ccltgXpI.o -R/home/sidney/.rvm/usr/lib -export-dynamic -R/home/sidney/.rvm/usr/lib -R /home/sidney/.rvm/rubies/ruby-2.0.0-p0/lib -lruby-static -lpthread -lrt -ldl -lcrypt -lm -lc -lgcc --as-needed -lgcc_s --no-as-needed -lc -lgcc --as-needed -lgcc_s --no-as-needed /usr/lib/gcc/x86_64-redhat-linux/4.7.2/crtend.o /usr/lib/gcc/x86_64-redhat-linux/4.7.2/../../../../lib64/crtn.o crash_function: _objalloc_alloc executable: /usr/bin/ld.bfd kernel: 3.7.9-201.fc18.x86_64 remote_result: NOTFOUND uid: 1000 var_log_messages: Feb 26 21:11:01 localhost abrt[16161]: Saved core dump of pid 16160 (/usr/bin/ld.bfd) to /var/spool/abrt/ccpp-2013-02-26-21:11:01-16160 (1781760 bytes) Truncated backtrace: Thread no. 1 (10 frames) #2 _objalloc_alloc at ./objalloc.c:152 #3 bfd_hash_allocate at hash.c:622 #4 bfd_section_hash_newfunc at section.c:752 #5 bfd_hash_insert at hash.c:509 #6 bfd_hash_lookup at hash.c:496 #7 bfd_make_section_anyway_with_flags at section.c:1124 #8 bfd_make_section_anyway at section.c:1171 #9 _bfd_elf_make_section_from_shdr at elf.c:827 #11 bfd_elf64_object_p at elfcode.h:808 #12 bfd_check_format_matches at format.c:202
Created attachment 703767 [details] File: backtrace
Created attachment 703768 [details] File: cgroup
Created attachment 703769 [details] File: core_backtrace
Created attachment 703770 [details] File: dso_list
Created attachment 703771 [details] File: environ
Created attachment 703772 [details] File: limits
Created attachment 703773 [details] File: maps
Created attachment 703774 [details] File: open_fds
Created attachment 703775 [details] File: proc_pid_status
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.