Version-Release number of selected component: gcc-c++-4.7.2-8.fc18 Additional info: backtrace_rating: 4 cmdline: /usr/libexec/gcc/x86_64-redhat-linux/4.7.2/cc1plus -quiet -D_GNU_SOURCE main.cpp -quiet -dumpbase main.cpp -mtune=generic -march=x86-64 -auxbase main -ggdb -Wall -Wextra -pedantic -std=c++11 -o - -frandom-seed=0 crash_function: linemap_macro_map_lookup executable: /usr/libexec/gcc/x86_64-redhat-linux/4.7.2/cc1plus kernel: 3.6.9-4.fc18.x86_64 remote_result: NOTFOUND uid: 1000 var_log_messages: Dec 10 14:03:53 localhost abrt[21349]: Saved core dump of pid 21348 (/usr/libexec/gcc/x86_64-redhat-linux/4.7.2/cc1plus) to /var/spool/abrt/ccpp-2012-12-10-14:03:50-21348 (121421824 bytes) Truncated backtrace: Thread no. 1 (10 frames) #14 linemap_macro_map_lookup at ../../libcpp/line-map.c:574 #15 linemap_macro_loc_to_def_point at ../../libcpp/line-map.c:953 #16 linemap_resolve_location at ../../libcpp/line-map.c:1072 #18 ?? #19 cp_diagnostic_starter at ../../gcc/cp/error.c:2834 #20 diagnostic_report_diagnostic at ../../gcc/diagnostic.c:548 #21 internal_error at ../../gcc/diagnostic.c:845 #22 crash_signal at ../../gcc/toplev.c:346 #24 tsubst at ../../gcc/cp/pt.c:11180 #26 instantiate_class_template_1 at ../../gcc/cp/pt.c:9010
Created attachment 660888 [details] File: backtrace
Created attachment 660889 [details] File: cgroup
Created attachment 660890 [details] File: core_backtrace
Created attachment 660891 [details] File: dso_list
Created attachment 660892 [details] File: environ
Created attachment 660893 [details] File: limits
Created attachment 660894 [details] File: maps
Created attachment 660895 [details] File: open_fds
Created attachment 660896 [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.