From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28808 invoked by alias); 27 May 2003 14:46:09 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 19700 invoked from network); 27 May 2003 14:41:33 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 27 May 2003 14:41:33 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id h4REfWH21429 for ; Tue, 27 May 2003 10:41:32 -0400 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [172.16.52.156]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id h4REfWI00300 for ; Tue, 27 May 2003 10:41:32 -0400 Received: from localhost.redhat.com (IDENT:Xw9nMxOWAu6QLi/nAPqa96/E0JpaEhfd@tooth.toronto.redhat.com [172.16.14.29]) by pobox.corp.redhat.com (8.11.6/8.11.6) with ESMTP id h4REfVo05527 for ; Tue, 27 May 2003 10:41:31 -0400 Received: by localhost.redhat.com (Postfix, from userid 469) id CB2762C43F; Tue, 27 May 2003 10:47:03 -0400 (EDT) From: Elena Zannoni MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16083.31335.661805.9131@localhost.redhat.com> Date: Tue, 27 May 2003 14:46:00 -0000 To: "H. J. Lu" Cc: GDB Subject: Re: RFC: DW_TAG_try_block In-Reply-To: <20030526124443.A7502@lucon.org> References: <20030526124443.A7502@lucon.org> X-SW-Source: 2003-05/txt/msg00351.txt.bz2 H. J. Lu writes: > Intel C++ compiler generates DW_TAG_try_block for > > try > { > ... > } > > Gdb can't print any local variables declared inside the try block. This > patch seems to work for us. Is that correct? > > > H.J. > --- > 2003-05-26 H.J. Lu > > * dwarf2read.c (process_die): Handle DW_TAG_try_block. > > --- gdb/dwarf2read.c.try 2003-05-26 12:23:22.000000000 -0700 > +++ gdb/dwarf2read.c 2003-05-26 12:37:08.000000000 -0700 > @@ -1768,6 +1768,7 @@ process_die (struct die_info *die, struc > of a function and make GDB `next' properly over inlined functions. */ > break; > case DW_TAG_lexical_block: > + case DW_TAG_try_block: > read_lexical_block_scope (die, objfile, cu_header); > break; > case DW_TAG_class_type: Seems ok, can you address Daniel's concern about the catch block? I.e. add that as well? How about adding a little test case to the gdb.c++ directory? elena