Bug 885745 - [abrt] gcc-c++-4.7.2-8.fc18: linemap_macro_map_lookup: Process /usr/libexec/gcc/x86_64-redhat-linux/4.7.2/cc1plus was killed by signal 6 (SIGABRT)
Summary: [abrt] gcc-c++-4.7.2-8.fc18: linemap_macro_map_lookup: Process /usr/libexec/g...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: gcc
Version: 18
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:79232ab0bc97400836ae5ed346b...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-10 14:13 UTC by Jan Teichmann
Modified: 2013-01-10 09:16 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-01-10 09:16:27 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (17.77 KB, text/plain)
2012-12-10 14:13 UTC, Jan Teichmann
no flags Details
File: cgroup (126 bytes, text/plain)
2012-12-10 14:13 UTC, Jan Teichmann
no flags Details
File: core_backtrace (5.93 KB, text/plain)
2012-12-10 14:14 UTC, Jan Teichmann
no flags Details
File: dso_list (938 bytes, text/plain)
2012-12-10 14:14 UTC, Jan Teichmann
no flags Details
File: environ (3.01 KB, text/plain)
2012-12-10 14:14 UTC, Jan Teichmann
no flags Details
File: limits (1.29 KB, text/plain)
2012-12-10 14:14 UTC, Jan Teichmann
no flags Details
File: maps (4.37 KB, text/plain)
2012-12-10 14:14 UTC, Jan Teichmann
no flags Details
File: open_fds (155 bytes, text/plain)
2012-12-10 14:14 UTC, Jan Teichmann
no flags Details
File: proc_pid_status (916 bytes, text/plain)
2012-12-10 14:14 UTC, Jan Teichmann
no flags Details

Description Jan Teichmann 2012-12-10 14:13:52 UTC
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

Comment 1 Jan Teichmann 2012-12-10 14:13:56 UTC
Created attachment 660888 [details]
File: backtrace

Comment 2 Jan Teichmann 2012-12-10 14:13:59 UTC
Created attachment 660889 [details]
File: cgroup

Comment 3 Jan Teichmann 2012-12-10 14:14:01 UTC
Created attachment 660890 [details]
File: core_backtrace

Comment 4 Jan Teichmann 2012-12-10 14:14:03 UTC
Created attachment 660891 [details]
File: dso_list

Comment 5 Jan Teichmann 2012-12-10 14:14:05 UTC
Created attachment 660892 [details]
File: environ

Comment 6 Jan Teichmann 2012-12-10 14:14:07 UTC
Created attachment 660893 [details]
File: limits

Comment 7 Jan Teichmann 2012-12-10 14:14:09 UTC
Created attachment 660894 [details]
File: maps

Comment 8 Jan Teichmann 2012-12-10 14:14:11 UTC
Created attachment 660895 [details]
File: open_fds

Comment 9 Jan Teichmann 2012-12-10 14:14:13 UTC
Created attachment 660896 [details]
File: proc_pid_status

Comment 10 Jan Teichmann 2013-01-10 09:16:27 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.