From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20759 invoked by alias); 28 Apr 2013 22:20:45 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 20738 invoked by uid 48); 28 Apr 2013 22:20:42 -0000 From: "synergye at codefi dot re" To: gcc-bugs@gcc.gnu.org Subject: [Bug libgcc/57085] Segmentation Fault when building a c file Date: Sun, 28 Apr 2013 22:20:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libgcc X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: synergye at codefi dot re X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 X-SW-Source: 2013-04/txt/msg02290.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57085 --- Comment #10 from synergye at codefi dot re 2013-04-28 22:20:42 UTC --- (In reply to comment #9) > (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? (In reply to comment #9) > (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? 1. The target triplet is arm-linux-androideabi 2. Building with a host triplet of i686-unknown-linux-gnu. Also used x86_64-unknown-linux-gnu. 3. The gcc sources are entirely vanilla trunk for testing.