Re: [rfa] annotate blocks with C++ namespace information

[Daniel Jacobowitz <drow@mvista.com>]

On Tue, Mar 11, 2003 at 02:58:56PM -0800, David Carlton wrote:
> On 11 Mar 2003 14:43:19 -0800, David Carlton <carlton@math.stanford.edu> said:
> > On Tue, 11 Mar 2003 16:23:13 -0500, Daniel Jacobowitz <drow@mvista.com> said:
> >> On Tue, Mar 11, 2003 at 01:14:16PM -0800, David Carlton wrote:
> 
> >>> Do any demanglers put in spaces after 'operator'?  I hope not...
> 
> >> I thought one of them did, but I might have been mistaken.
> 
> > You could easily be right: I haven't done a lot of GCC v2 checking.
> > I'll look into that, and, if so, add a guard for a possible extra
> > space in cp_find_first_component.
> 
> Yeah, I'll add it: with gcc 2.95.3 -gdwarf-2, I get:
> 
> 	.ascii "operator ->\0"	# DW_AT_name
> 	.byte	0x1	# DW_AT_decl_file
> 	.byte	0x3	# DW_AT_decl_line
> 	.ascii "__rf__1C\0"	# DW_AT_MIPS_linkage_name
> 
> and while the demangler doesn't put in a space when demangling
> __rf__1C, there's still that space in the DW_AT_name.  And while I
> think that most internal uses of operator names within GDB will come
> via the demangler, it's probably not wise to bet that they all do.

Good.  Especially since, going forward, more of them will not come via
the demangler.  I'm just waiting for better namespace handling to
settle in before I get back to that.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer