public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/51384] New: seg fault in tsubst_copy_and_build Date: Thu, 01 Dec 2011 21:00:00 -0000 [thread overview] Message-ID: <bug-51384-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51384 Bug #: 51384 Summary: seg fault in tsubst_copy_and_build Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: dcb314@hotmail.com I just tried to compile the package eigen3-3.0.0 on latest trunk snapshot 20111126 on an AMD x86_64 box. The compiler said /home/dcb/rpmbuild/BUILD/eigen-eigen-65ee2328342f/Eigen/src/Core/DenseBase.h:247:137: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. Here is valgrind helping out with a stack bracktrace ==13212== Invalid read of size 2 ==13212== at 0x55AC74: tsubst_copy_and_build(tree_node*, tree_node*, int, tree_node*, bool, bool) (pt.c:13374) ==13212== by 0x559F36: tsubst_copy_and_build(tree_node*, tree_node*, int, tree_node*, bool, bool) (pt.c:13889) ==13212== by 0x5591BA: tsubst_copy_and_build(tree_node*, tree_node*, int, tree_node*, bool, bool) (pt.c:13367) ==13212== by 0x559DB3: tsubst_copy_and_build(tree_node*, tree_node*, int, tree_node*, bool, bool) (pt.c:13519) ==13212== by 0x54A350: tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool) (pt.c:13245) ==13212== by 0x56517D: tsubst_template_arg(tree_node*, tree_node*, int, tree_node*) (pt.c:9187) ==13212== by 0x56DF3E: coerce_template_parms(tree_node*, tree_node*, tree_node*, int, bool, bool) (pt.c:6846) ==13212== by 0x552A4E: lookup_template_class(tree_node*, tree_node*, tree_node*, tree_node*, int, int) (pt.c:7375) ==13212== by 0x658332: finish_template_type(tree_node*, tree_node*, int) (semantics.c:2760) ==13212== by 0x5EFD18: cp_parser_template_id(cp_parser*, bool, bool, bool) (parser.c:12445) ==13212== by 0x5F01AF: cp_parser_class_name(cp_parser*, bool, bool, tag_types, bool, bool, bool) (parser.c:17876) ==13212== by 0x5EA699: cp_parser_nested_name_specifier_opt(cp_parser*, bool, bool, bool, bool) (parser.c:5249) ==13212== Address 0x0 is not stack'd, malloc'd or (recently) free'd ==13212== Preprocessed source code attached. Flag -march=native required.
next reply other threads:[~2011-12-01 21:00 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-12-01 21:00 dcb314 at hotmail dot com [this message] 2011-12-01 21:02 ` [Bug c++/51384] " dcb314 at hotmail dot com 2011-12-01 21:55 ` paolo.carlini at oracle dot com 2011-12-06 14:25 ` 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-51384-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: linkBe 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).