From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23094 invoked by alias); 15 Feb 2002 23:29:20 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 23027 invoked from network); 15 Feb 2002 23:29:19 -0000 Received: from unknown (HELO d0sgibnl1.fnal.gov) (131.225.226.68) by sources.redhat.com with SMTP; 15 Feb 2002 23:29:19 -0000 Received: (from snyder@localhost) by d0sgibnl1.fnal.gov (SGI-8.9.3/8.9.3) id RAA67487; Fri, 15 Feb 2002 17:29:17 -0600 (CST) X-Authentication-Warning: d0sgibnl1.fnal.gov: snyder set sender to snyder@fnal.gov using -f To: Daniel Jacobowitz Cc: gdb-patches@sources.redhat.com Subject: Re: PATCH to avoid infinite loop in cplus-dem.c on some EDG names References: <200202152231.QAA69091@d0sgibnl1.fnal.gov> <20020215173626.A8937@nevyn.them.org> From: Scott Snyder Date: Fri, 15 Feb 2002 15:29:00 -0000 In-Reply-To: <20020215173626.A8937@nevyn.them.org> Message-ID: User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Bryce Canyon) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2002-02/txt/msg00438.txt.bz2 >>>>> "Daniel" == Daniel Jacobowitz writes: Daniel> Thanks for the patch - but demangler patches need to go to Daniel> gcc-patches@gcc.gnu.org. The demangler is maintained Daniel> outside of GDB. Thanks --- i wasn't completely sure where was appropriate. I've sent another copy there. Daniel> Are you testing C++ support on this compiler? I'd be Daniel> quite surprised if it worked - though not unpleasantly. I've used gcc 4.18 with that compiler for quite a while. It doesn't really understand the C++ stuff, but it works well enough to be useful. With gdb 5, though, i started seeing this problem with gdb sometimes getting stuck reading in EDG symbols. (Actually, i first reported this in sept. 99 in reference to the SGI C++ compiler; i didn't send a patch at that point though). KAI now has their own set of patches to gdb 5, but it would be nice to be able to do something useful with the standard version. (Plus, i saw this problem occur once even in their patched version.) thanks, sss