Version-Release number of selected component: glibc-2.17-11.fc19 Additional info: reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: /lib64/ld-linux-x86-64.so.2 /usr/lib64/libcairo.so.2.11200.14 crash_function: elf_machine_rela executable: /usr/lib64/ld-2.17.so kernel: 3.9.8-300.fc19.x86_64 runlevel: N 5 uid: 0 Truncated backtrace: Thread no. 1 (8 frames) #0 elf_machine_rela at ../sysdeps/x86_64/dl-machine.h:395 #1 elf_dynamic_do_Rela at do-rel.h:137 #2 _dl_relocate_object at dl-reloc.c:295 #3 _dl_receive_error at dl-error.c:209 #4 dl_main at rtld.c:1959 #5 _dl_sysdep_start at ../elf/dl-sysdep.c:241 #6 _dl_start_final at rtld.c:329 #7 _dl_start at rtld.c:555 Potential duplicate: bug 922446
Created attachment 768024 [details] File: backtrace
Created attachment 768025 [details] File: cgroup
Created attachment 768026 [details] File: core_backtrace
Created attachment 768027 [details] File: dso_list
Created attachment 768028 [details] File: environ
Created attachment 768029 [details] File: limits
Created attachment 768030 [details] File: maps
Created attachment 768031 [details] File: open_fds
Created attachment 768032 [details] File: proc_pid_status
Created attachment 768033 [details] File: var_log_messages
The crash is while updating an R_X86_64_64 relocation. We shouldn't crash if the relocations are valid. The most likely case is that the program stomped all over the stack and this crash is a result of a corrupted stack. Is this reproducible?
Folks, I think this turned out to be a false alarm, at least my bug report. A change of RAM seemed to have cleared all the numerous problems I was experiencing with Fedora 19 on my new system build. Apologies for the false alarm, and thanks for all the work you debuggers put in for the rest of us. A. King
Thanks for confirming that this was a hardware issue. We've seen a lot of these problems in elf_machine_rela but we almost always track them down to program corruption. I'm marking this CLOSED/NOTABUG, please file a new issue if you run into this again.