From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13438 invoked by alias); 4 May 2009 14:43:29 -0000 Received: (qmail 13386 invoked by uid 48); 4 May 2009 14:43:15 -0000 Date: Mon, 04 May 2009 14:43:00 -0000 Message-ID: <20090504144315.13385.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug bootstrap/39849] segfault for '__divtf3' during bootstrap and non-bootstrap install In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "dennis dot wassel at googlemail dot com" 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 X-SW-Source: 2009-05/txt/msg00234.txt.bz2 ------- Comment #12 from dennis dot wassel at googlemail dot com 2009-05-04 14:43 ------- (In reply to comment #10) > It obviously works for me, you system seems to be messed up / special. Seems so, although it is a Debian 4 with an unknown amount of modifications by our admin. One symptom of specialness is the fact that neither the system nor the gcc's headers define SSIZE_MAX, but I have a workaround for that (namely defining it as SHRT_MAX in config/host-linux.c, if it is undefined). Shall I dig around somewhere to find out the exact amount of my system's specialness? Is there a way to build the bootstrap compiler with debugging info, so I can use gdb to figure out where the segfault happens? PS: I think this *is* a regression, because I can build 4.3, but not 4.4. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39849