public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vogt at linux dot vnet.ibm.com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug go/67968] go1: internal compiler error: in write_specific_type_functions, at go/gofrontend/types.cc:1812 Date: Fri, 23 Oct 2015 12:38:00 -0000 [thread overview] Message-ID: <bug-67968-4-tRN5lYTERD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-67968-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67968 --- Comment #5 from Dominik Vogt <vogt at linux dot vnet.ibm.com> --- Unfortunately I cannot reproduce this yet. Please try to identify the "faulty" source file and strip it down to the minimum. 1. Find out in which file the ICE occurs. 1.a Recompile GCC with debug information, e.g. with $ make CXXFLAGS="-g3 -O2" CFLAGS="$CXXFLAGS" GOCFLAGS="$CXXFLAGS" -j 7 all 1.b Use the commands from comment 4 to run the gccgo-5 command line manually. This whould still generate an ICE. 1.c Run the go1 command in gdb. Just add the option -wrapper gdb,--args at the end of the gccgo-5 command line. Then type "run" in the debugger. Gdb should automatically stop when the ICE occurs. From there, check the available information in the current stack frame and the higher ones and see if you can find the name of the current source file or the function name and possibly the line number in some structure. I know nothing about the Go frontent, so unfortunately you have to figure that out on your own. 2. Strip down the sources as much as possible. Now that you know which file generates the ICE, try to strip down the api module as much as possible. The first step is to get rid of all the other files in the package. Next, remove the imports in the faulty file and finally strip down the file as much as possible to make a standalone test case.
next prev parent reply other threads:[~2015-10-23 12:38 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-10-14 17:25 [Bug go/67968] New: " gong_su at hotmail dot com 2015-10-15 14:06 ` [Bug go/67968] " vogt at linux dot vnet.ibm.com 2015-10-22 9:45 ` vogt at linux dot vnet.ibm.com 2015-10-23 12:38 ` vogt at linux dot vnet.ibm.com [this message] 2015-10-23 12:39 ` vogt at linux dot vnet.ibm.com 2015-10-23 16:59 ` ian at airs dot com 2015-10-23 17:08 ` vogt at linux dot vnet.ibm.com 2015-10-23 17:42 ` ian at airs dot com 2015-10-26 12:03 ` vogt at linux dot vnet.ibm.com 2015-10-27 10:21 ` vogt at linux dot vnet.ibm.com 2015-10-28 15:44 ` gong_su at hotmail dot com
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-67968-4-tRN5lYTERD@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).