This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
Re: c++/932: GDB is not able to show parameters of catch block
- From: "Sysoltsev, Vyatcheslav" <vyatcheslav dot sysoltsev at intel dot com>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 5 Aug 2003 09:58:00 -0000
- Subject: Re: c++/932: GDB is not able to show parameters of catch block
- Reply-to: "Sysoltsev, Vyatcheslav" <vyatcheslav dot sysoltsev at intel dot com>
The following reply was made to PR c++/932; it has been noted by GNATS.
From: "Sysoltsev, Vyatcheslav" <vyatcheslav.sysoltsev@intel.com>
To: <gdb-gnats@sources.redhat.com>
Cc:
Subject: Re: c++/932: GDB is not able to show parameters of catch block
Date: Tue, 5 Aug 2003 13:52:13 +0400
http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=3Dview%20audit-trail&da=
tabase=3Dgdb&pr=3D932
Hi there!
I came across this problem too and noticed that there were no advances =
in solving for about half a year.
So I took a quick look at the issue and develop a naive patch to =
gdb/dwarf2read.c:
--- gdb/dwarf2read.c.orig 2003-08-05 12:35:34.000000000 +0400
+++ gdb/dwarf2read.c 2003-08-05 12:35:44.000000000 +0400
@@ -1494,6 +1494,7 @@
of a function and make GDB `next' properly over inlined =
functions. */
break;
case DW_TAG_lexical_block:
+ case DW_TAG_catch_block:
read_lexical_block_scope (die, objfile, cu_header);
break;
case DW_TAG_class_type:
Gdb with this patch works well not exposing the problem described in =
tracker 932 but I haven't performed any extensive testing because I am =
not familiar with gdb development.
Comrades developers, please verify the fix or do anything constructive =
to solve the problem.
-- Slava