From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 684 invoked by alias); 4 Nov 2002 16:56:04 -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 635 invoked by uid 71); 4 Nov 2002 16:56:04 -0000 Date: Mon, 04 Nov 2002 08:56:00 -0000 Message-ID: <20021104165604.612.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Wolfgang Bangerth Subject: Re: c++/8442: Wrongful compiler error - file available Reply-To: Wolfgang Bangerth X-SW-Source: 2002-11/txt/msg00166.txt.bz2 List-Id: The following reply was made to PR c++/8442; it has been noted by GNATS. From: Wolfgang Bangerth To: Juan Carlos Arevalo-Baeza Cc: gcc-bugs@gcc.gnu.org, , , Subject: Re: c++/8442: Wrongful compiler error - file available Date: Mon, 4 Nov 2002 10:58:35 -0600 (CST) > Yes, Spirit is a complex beast. I'm sorry about that. I've tried > extracting the error bits, but I've been uncuccessful so far. It seems Start from the .ii file you have. First delete all the # lines, I use the following perl script for that usually perl -pi -s 's/^#.*\n//g;' your_file.ii (This way, gcc tells you the real location in the file where something is happening, not the location in the file from which you generated the .ii file.) Then start deleting parts of the file that are not necessary to show the problem. (Function bodies, classes that are only referenced in the function bodies you deleted, classes and namespaces that were only used in classes and namespaces you deleted, etc). In the beginning, the pieces you scrap are usually small, but the blocks can become very large at the end, so don't be scared if you don't make much progress in the beginning. This is a tedious task, and may take an hour or two, but in the end you usually end up with something that has 10-50 lines of code and still shows the problem. With such an example, it is also possible for someone who is not used to your code to see whether this is wrong or right. Otherwise, it is very hard to see... Regards Wolfgang ------------------------------------------------------------------------- Wolfgang Bangerth email: bangerth@ticam.utexas.edu www: http://www.ticam.utexas.edu/~bangerth