From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18985 invoked by alias); 14 Apr 2003 20:12:01 -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 18961 invoked from network); 14 Apr 2003 20:12:00 -0000 Received: from unknown (HELO jackfruit.Stanford.EDU) (171.64.38.136) by sources.redhat.com with SMTP; 14 Apr 2003 20:12:00 -0000 Received: (from carlton@localhost) by jackfruit.Stanford.EDU (8.11.6/8.11.6) id h3EKBrv21542; Mon, 14 Apr 2003 13:11:53 -0700 X-Authentication-Warning: jackfruit.Stanford.EDU: carlton set sender to carlton@math.stanford.edu using -f To: Andrew Cagney Cc: Daniel Jacobowitz , gdb-patches@sources.redhat.com Subject: Re: PATCH: Remove ancient GNU catch catch/catch throw support References: <20030325030555.GA6101@nevyn.them.org> <3E807451.6050009@redhat.com> From: David Carlton Date: Mon, 14 Apr 2003 20:12:00 -0000 In-Reply-To: <3E807451.6050009@redhat.com> Message-ID: User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Common Lisp) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-04/txt/msg00294.txt.bz2 [ Going through old e-mail. ] On Tue, 25 Mar 2003 10:22:57 -0500, Andrew Cagney said: >> This is for either g++ 1.x or early 2.x; it doesn't work for 2.95 which is >> the oldest C++ compiler we're interested in supporting. I'll commit this in >> a day or so unless anyone has a good reason not to. > The statement that GDB doesn't support anything before 2.95 should > also be formalized. At present there isn't anything in writing :-( There is the following statement in gdb.texinfo: Currently, @value{GDBN} works best when debugging C@t{++} code that is compiled with @value{NGCC} 2.95.3 or with @value{NGCC} 3.1 or newer, using the options @option{-gdwarf-2} or @option{-gstabs+}. DWARF 2 is preferred over stabs+. Most configurations of @value{NGCC} emit either DWARF 2 or stabs+ as their default debug format, so you usually don't need to specify a debug format explicitly. Other compilers and/or debug formats are likely to work badly or not at all when using @value{GDBN} to debug C@t{++} code. But it probably should be mentioned more prominently somewhere. I'm not sure exactly what we want to say: we're not going through and ripping out support for HP's C++ compiler, after all. (At least not yet...) David Carlton carlton@math.stanford.edu