From: Daniel Jacobowitz <drow@mvista.com>
To: "H. J. Lu" <hjl@lucon.org>
Cc: GDB <gdb@sources.redhat.com>
Subject: Re: RFC: DW_TAG_try_block
Date: Mon, 26 May 2003 19:59:00 -0000 [thread overview]
Message-ID: <20030526195646.GA26902@nevyn.them.org> (raw)
In-Reply-To: <20030526124443.A7502@lucon.org>
On Mon, May 26, 2003 at 12:44:43PM -0700, H. J. Lu wrote:
> 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?
I believe that this is correct, and that (at least for now) the same
thing should be done for DW_TAG_catch_block. There's a PR for this
issue.
[But wait for a DWARF maintainer to comment, please.]
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-05-26 19:59 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 [this message]
2003-05-26 20:16 ` H. J. Lu
2003-05-27 14:46 ` Elena Zannoni
2003-05-27 14:58 ` H. J. Lu
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=20030526195646.GA26902@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=hjl@lucon.org \
/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).