public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mikpe at it dot uu.se" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcc/57085] Segmentation Fault when building a c file
Date: Sun, 28 Apr 2013 18:08:00 -0000 [thread overview]
Message-ID: <bug-57085-4-MArygseJ4B@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57085-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57085
--- Comment #9 from Mikael Pettersson <mikpe at it dot uu.se> 2013-04-28 18:08:02 UTC ---
(In reply to comment #8)
> Any suggestions for
> troubleshooting this bug on my end? I've done a few toolchain builds and always
> run into this segfault as do others.
Tell us more about the host and target system:
1. What's the complete target triplet?
2. What's the host system's triplet? You only wrote "i686", but the OS part
may be relevant (Linux, *BSD, MacOS, Cygwin, MinGW, ...).
3. Are the gcc sources completely vanilla, or do you have local modifications?
next prev parent reply other threads:[~2013-04-28 18:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 18:23 [Bug libgcc/57085] New: " synergye at codefi dot re
2013-04-27 22:54 ` [Bug libgcc/57085] " synergye at codefi dot re
2013-04-28 9:11 ` mikpe at it dot uu.se
2013-04-28 10:18 ` ubizjak at gmail dot com
2013-04-28 10:18 ` synergye at codefi dot re
2013-04-28 13:41 ` mikpe at it dot uu.se
2013-04-28 17:51 ` synergye at codefi dot re
2013-04-28 18:08 ` mikpe at it dot uu.se [this message]
2013-04-28 22:20 ` synergye at codefi dot re
2013-04-29 19:30 ` mikpe at it dot uu.se
2013-04-29 21:13 ` synergye at codefi dot re
2013-05-03 9:23 ` synergye at codefi dot re
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-57085-4-MArygseJ4B@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).