public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin.liska at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/60553] New: segfault in gt_ggc_mx_lang_tree_node in Chromium with LTO
Date: Mon, 17 Mar 2014 14:54:00 -0000 [thread overview]
Message-ID: <bug-60553-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60553
Bug ID: 60553
Summary: segfault in gt_ggc_mx_lang_tree_node in Chromium with
LTO
Product: gcc
Version: 4.9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin.liska at gmail dot com
I do compile Chromium with LTO and there's ICE with enormous call stack:
gcc --version:
gcc (GCC) 4.9.0 20140313 (experimental)
ld --version:
GNU gold (GNU Binutils 2.24.51.20140304) 1.11
(gdb) bt -20
#529301 0x00000000005aae8e in gt_ggc_mx_lang_tree_node (x_p=0x7f5c763af738) at
./gtype-lto.h:359
#529302 0x00000000005aaf8b in gt_ggc_mx_lang_tree_node (x_p=0x7f5c644eedc8) at
./gtype-lto.h:378
#529303 0x00000000005aae8e in gt_ggc_mx_lang_tree_node (x_p=0x7f5c763a40a8) at
./gtype-lto.h:359
#529304 0x00000000005a92ef in gt_ggc_mx_lang_tree_node (x_p=0x7f5c763a70c0) at
./gtype-lto.h:55
#529305 0x00000000005aae54 in gt_ggc_mx_lang_tree_node (x_p=0x7f5c763a4150) at
./gtype-lto.h:357
#529306 0x00000000005a92ef in gt_ggc_mx_lang_tree_node (x_p=0x7f5c763a73a0) at
./gtype-lto.h:55
#529307 0x00000000005aae37 in gt_ggc_mx_lang_tree_node (x_p=0x7f5c763a4690) at
./gtype-lto.h:356
#529308 0x00000000005aadfd in gt_ggc_mx_lang_tree_node (x_p=0x7f5c763c2c78) at
./gtype-lto.h:354
#529309 0x00000000005aa694 in gt_ggc_mx_lang_tree_node (x_p=0x7f5c7650fc00) at
./gtype-lto.h:263
#529310 0x0000000000821c23 in gt_ggc_m_P9tree_node4htab (x_p=0x7f5c7775a850) at
gtype-desc.c:3185
#529311 0x00000000007bfde6 in ggc_mark_root_tab (rt=0x10cd140
<gt_ggc_r_gt_optabs_h>) at ../../gcc/ggc-common.c:133
#529312 0x00000000007c0281 in ggc_mark_roots () at ../../gcc/ggc-common.c:152
#529313 0x00000000005d0c2a in ggc_collect () at ../../gcc/ggc-page.c:2077
#529314 0x00000000005c32e7 in read_cgraph_and_symbols (nfiles=11258,
fnames=0x36701f0) at ../../gcc/lto/lto.c:3004
#529315 0x00000000005c406a in lto_main () at ../../gcc/lto/lto.c:3406
#529316 0x00000000009e4273 in compile_file () at ../../gcc/toplev.c:548
#529317 0x00000000009e640a in do_compile () at ../../gcc/toplev.c:1914
#529318 0x00000000009e6575 in toplev_main (argc=11283, argv=0x35fe750) at
../../gcc/toplev.c:1990
#529319 0x00007f5c765b6be5 in __libc_start_main () from /lib64/libc.so.6
#529320 0x0000000000587831 in _start () at ../sysdeps/x86_64/start.S:122
(gdb) bt 10
#0 0x00000000005cec2c in lookup_page_table_entry (p=<error reading variable:
Cannot access memory at address 0x7fffa80e8fc8>) at ../../gcc/ggc-page.c:584
#1 0x00000000005cfc5e in ggc_set_mark (p=0x7f5c399c1170) at
../../gcc/ggc-page.c:1467
#2 0x00000000005a9222 in gt_ggc_mx_lang_tree_node (x_p=0x7f5c399c1170) at
./gtype-lto.h:36
#3 0x00000000005aae1a in gt_ggc_mx_lang_tree_node (x_p=0x7f5c399c6f18) at
./gtype-lto.h:355
#4 0x00000000005aaf34 in gt_ggc_mx_lang_tree_node (x_p=0x7f5c399c6e70) at
./gtype-lto.h:375
#5 0x00000000005aa4b8 in gt_ggc_mx_lang_tree_node (x_p=0x7f5c399c10b8) at
./gtype-lto.h:246
#6 0x00000000005aaf17 in gt_ggc_mx_lang_tree_node (x_p=0x7f5c399c60a8) at
./gtype-lto.h:374
#7 0x00000000005aaf34 in gt_ggc_mx_lang_tree_node (x_p=0x7f5c399bf5e8) at
./gtype-lto.h:375
#8 0x00000000005aa461 in gt_ggc_mx_lang_tree_node (x_p=0x7f5c399bae60) at
./gtype-lto.h:243
#9 0x00000000005aaf17 in gt_ggc_mx_lang_tree_node (x_p=0x7f5c399bf348) at
./gtype-lto.h:374
I don't know what to dump, if you are interested I can add all kind info you
need.
next reply other threads:[~2014-03-17 14:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-17 14:54 marxin.liska at gmail dot com [this message]
2014-03-17 15:23 ` [Bug c++/60553] " rguenth at gcc dot gnu.org
2014-03-17 15:45 ` marxin.liska at gmail dot com
2014-03-18 10:28 ` rguenth at gcc dot gnu.org
2014-03-18 11:00 ` rguenth at gcc dot gnu.org
2014-03-18 15:33 ` marxin.liska at gmail dot com
2014-03-19 13:04 ` rguenth at gcc dot gnu.org
2014-03-19 15:38 ` rguenth at gcc dot gnu.org
2014-03-19 16:42 ` marxin.liska at gmail dot com
2014-03-20 9:11 ` rguenth at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-60553-4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).