From: "H. J. Lu" <hjl@lucon.org>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: GDB <gdb@sources.redhat.com>
Subject: Re: RFC: DW_TAG_try_block
Date: Tue, 27 May 2003 14:58:00 -0000 [thread overview]
Message-ID: <20030527075736.A22991@lucon.org> (raw)
In-Reply-To: <16083.31335.661805.9131@localhost.redhat.com>; from ezannoni@redhat.com on Tue, May 27, 2003 at 10:47:03AM -0400
On Tue, May 27, 2003 at 10:47:03AM -0400, Elena Zannoni wrote:
> 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 <hongjiu.lu@intel.com>
> >
> > * 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?
http://sources.redhat.com/ml/gdb/2003-05/msg00348.html
> How about adding a little test case to the gdb.c++ directory?
>
I can provide a simple C++ code. But you will need Intel C++ compiler to
see the problem. Also the current Intel compiler doesn't support RedHat
9.
H.J.
next prev parent reply other threads:[~2003-05-27 14:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-26 19:46 H. J. Lu
2003-05-26 19:59 ` Daniel Jacobowitz
2003-05-26 20:16 ` H. J. Lu
2003-05-27 14:46 ` Elena Zannoni
2003-05-27 14:58 ` H. J. Lu [this message]
2003-05-27 15:05 ` Daniel Jacobowitz
2003-05-27 15:06 ` Elena Zannoni
2003-05-27 15:19 ` H. J. Lu
2003-05-28 16:47 ` David Carlton
2003-05-28 16:50 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030527075736.A22991@lucon.org \
--to=hjl@lucon.org \
--cc=ezannoni@redhat.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).