Version-Release number of selected component: elfutils-0.155-1.fc18 Additional info: backtrace_rating: 4 cmdline: eu-unstrip --core=./coredump -n crash_function: elf_end executable: /usr/bin/eu-unstrip kernel: 3.6.9-4.fc18.x86_64 open_fds: remote_result: NOTFOUND uid: 0 Truncated backtrace: Thread no. 1 (4 frames) #0 elf_end at elf_end.c:174 #1 free_file at dwfl_module.c:52 #2 __libdwfl_module_free at dwfl_module.c:81 #3 dwfl_end at dwfl_end.c:46
Created attachment 662497 [details] File: backtrace
Created attachment 662498 [details] File: build_ids
Created attachment 662499 [details] File: cgroup
Created attachment 662500 [details] File: environ
Created attachment 662501 [details] File: limits
Created attachment 662502 [details] File: maps
Created attachment 662503 [details] File: proc_pid_status
I noticed more strange memory corruption in other programs recently and as it turned out I had a defective RAM module. Effects were very random and rare but could be the cause of most memory corruption I lately reported. I assumed it is related to the beta state of F18 so I didnt suspect the RAM at first but MemTest found a small address range with errors. I am extremely sorry for taking up your time hunting down bugs which are most likely not there. I decided to close my latest bug reports as I can not assure that the memory corruption was actually caused by the program rather than the defect RAM module.