Re: RFC: DW_TAG_try_block

H. J. Lu
2003-05-26T20:16:29Z

On Mon, May 26, 2003 at 03:56:46PM -0400, Daniel Jacobowitz wrote:
> 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.
>

You are right. We do use DW_TAG_catch_block. This also works for the
catch block.

H.J.
---
2003-05-26 H.J. Lu <hongjiu.lu@intel.com>

* dwarf2read.c (process_die): Handle DW_TAG_try_block and
DW_TAG_catch_block.

--- gdb/dwarf2read.c.try 2003-05-26 12:23:22.000000000 -0700
+++ gdb/dwarf2read.c 2003-05-26 13:07:47.000000000 -0700
@@ -1768,6 +1768,8 @@ 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:
+ case DW_TAG_catch_block:
read_lexical_block_scope (die, objfile, cu_header);
break;