aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDavid Carlton <carlton@bactrian.org>2003-12-15 21:28:54 +0000
committerDavid Carlton <carlton@bactrian.org>2003-12-15 21:28:54 +0000
commita8970facae7aaf63d5815798879c87d3a172344b (patch)
tree100f7dccdd8d5396648c65a94a1c46255def3e6f
parent3b14be589cafdff0e8bfb3daca46e6dffd657711 (diff)
downloadgdb-a8970facae7aaf63d5815798879c87d3a172344b.zip
gdb-a8970facae7aaf63d5815798879c87d3a172344b.tar.gz
gdb-a8970facae7aaf63d5815798879c87d3a172344b.tar.bz2
Fix comment in last commit.
-rw-r--r--gdb/dwarf2read.c10
1 files changed, 6 insertions, 4 deletions
diff --git a/gdb/dwarf2read.c b/gdb/dwarf2read.c
index a42144b..33146a8 100644
--- a/gdb/dwarf2read.c
+++ b/gdb/dwarf2read.c
@@ -2573,10 +2573,12 @@ get_scope_pc_bounds (struct die_info *die,
case DW_TAG_namespace:
/* FIXME: carlton/2003-12-15: Should we do this for
DW_TAG_class_type/DW_TAG_structure_type, too? I think
- that current GCC's always generate the DIEs
- corresponding to definitions methods of classes at
- namespace scope, but I don't see any reason why they
- have to. */
+ that current GCC's always emit the DIEs corresponding
+ to definitions of methods of classes as children of a
+ DW_TAG_compile_unit or DW_TAG_namespace (as opposed to
+ the DIEs giving the declarations, which could be
+ anywhere). But I don't see any reason why they have to
+ be there. */
get_scope_pc_bounds (child, &current_low, &current_high,
objfile, cu_header);