From owner-freebsd-hackers Fri Apr 25 10:34:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA29145 for hackers-outgoing; Fri, 25 Apr 1997 10:34:43 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA29140 for ; Fri, 25 Apr 1997 10:34:20 -0700 (PDT) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0wKosS-0003wb-00; Fri, 25 Apr 1997 11:33:44 -0600 To: Nanbor Wang Subject: Re: Any compiler guru? (Was: 2 questions about C++ support in 2.2) Cc: hackers@freebsd.org In-reply-to: Your message of "Thu, 24 Apr 1997 23:32:56 CDT." <199704250432.XAA11988@siesta.cs.wustl.edu> References: <199704250432.XAA11988@siesta.cs.wustl.edu> Date: Fri, 25 Apr 1997 11:33:44 -0600 From: Warner Losh Message-Id: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199704250432.XAA11988@siesta.cs.wustl.edu> Nanbor Wang writes: : > : ACE. After spitting out a lot of GOT warnings, the compiler finally : > : spited out "Compiler internal error" and went dead. : > : > Hmmm, that's bad. I don't think that is related to the above : > messages. : : Any recommendation where to look first? I am totally clueless. All : g++ said was internal error. ;( Hmmm, then it is a g++ for sure :-) What I usually did when I encountered something like this was to do a binary search until I found the line(s) that caused the problem(s), and then submitted bug reported based on that. Generally, but not always, I was able to kludge around the problem. Warner