From 2a35147e4a88775fe96037345ab9f54fb10d3a1e Mon Sep 17 00:00:00 2001 From: Jim Blandy Date: Wed, 28 Jan 2004 04:05:22 +0000 Subject: * dwarf2read.c (read_func_scope): Re-indent comment. --- gdb/dwarf2read.c | 42 +++++++++++++++++++++--------------------- 1 file changed, 21 insertions(+), 21 deletions(-) (limited to 'gdb/dwarf2read.c') diff --git a/gdb/dwarf2read.c b/gdb/dwarf2read.c index 94d210c..c5fbd5d 100644 --- a/gdb/dwarf2read.c +++ b/gdb/dwarf2read.c @@ -2173,27 +2173,27 @@ read_func_scope (struct die_info *die, struct dwarf2_cu *cu) { struct die_info *spec_die = die_specification (die, cu); - /* NOTE: carlton/2004-01-23: We have to be careful in the - presence of DW_AT_specification. For example, with GCC - 3.4, given the code - - namespace N { - void foo() { - // Definition of N::foo. - } - } - - then we'll have a tree of DIEs like this: - - 1: DW_TAG_compile_unit - 2: DW_TAG_namespace // N - 3: DW_TAG_subprogram // declaration of N::foo - 4: DW_TAG_subprogram // definition of N::foo - DW_AT_specification // refers to die #3 - - Thus, when processing die #4, we have to pretend that - we're in the context of its DW_AT_specification, namely - the contex of die #3. */ + /* NOTE: carlton/2004-01-23: We have to be careful in the + presence of DW_AT_specification. For example, with GCC 3.4, + given the code + + namespace N { + void foo() { + // Definition of N::foo. + } + } + + then we'll have a tree of DIEs like this: + + 1: DW_TAG_compile_unit + 2: DW_TAG_namespace // N + 3: DW_TAG_subprogram // declaration of N::foo + 4: DW_TAG_subprogram // definition of N::foo + DW_AT_specification // refers to die #3 + + Thus, when processing die #4, we have to pretend that we're + in the context of its DW_AT_specification, namely the contex + of die #3. */ if (spec_die != NULL) { -- cgit v1.1