From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28307 invoked by alias); 21 Dec 2002 03:20:50 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 28288 invoked by uid 61); 21 Dec 2002 03:20:50 -0000 Date: Fri, 20 Dec 2002 19:20:00 -0000 Message-ID: <20021221032050.28287.qmail@sources.redhat.com> To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, patsmith@pobox.com From: bangerth@dealii.org Reply-To: bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, patsmith@pobox.com, gcc-gnats@gcc.gnu.org Subject: Re: optimization/9015: bc segfaults when compiled with optimization X-SW-Source: 2002-12/txt/msg01137.txt.bz2 List-Id: Synopsis: bc segfaults when compiled with optimization State-Changed-From-To: open->feedback State-Changed-By: bangerth State-Changed-When: Fri Dec 20 19:20:49 2002 State-Changed-Why: It is very hard for us to reproduce a problem with such little information, since we don't really know what we're looking for. Sometimes such problems go away by moving to a different platform, and then we would not be able to reproduce it. Basically, a whole program is too large for us to find a bug in. What you could do is the following: try to run bc under a debugger and try to find out which function it crashes in by looking at a stacktrace after the crash happens. Then try to isolate the function in which this happens from the rest of the program and see whether you can come up with a small testcase from which we can work on. This would ideally just include the one function in which things happen, called from a dummy main function. Thanks Wolfgang http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9015