This is the mail archive of the gdb-prs@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: gdb/1465


The following reply was made to PR c++/1465; it has been noted by GNATS.

From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: carlton@kealia.com, mec.gnu@mindspring.com
Cc: gdb-gnats@sources.redhat.com
Subject: Re: gdb/1465
Date: Wed, 26 Nov 2003 16:38:08 -0500 (EST)

 Hi David,
 
 > Right.  But, as I just e-mailed in a separate thread, I think this is
 > part of the problem here - this symbol shouldn't be in a static block,
 > it should be in a global block.  And my latest patch awaiting
 > approval, among other things, puts it in a global block.
 
 But what about:
 
   int foo ()
   {
     class A { ... };
   }
 
   int bar ()
   {
     class A { ... ... };
   }
 
 Classes are scoped.  Wouldn't you have to do a bunch of work to make
 sure that the namespace lookup works properly if all the symbols live
 in global symtabs?
 
 dc> There's always get_selected_block (0), or whatever it's called.  But
 dc> I'm not sure that that will always be the correct thing to do.
 
 That sounds good.  I'll look around there.
 
 mec> (1) Change gnuv2_value_rtti_type from lookup_typename to
 mec>     lookup_symbol.
 
 dc> Yeah.
 
 Okay, that sounds unambiguously good.  And it's only for gnuv2
 so I can be sure that I'm not breaking something anything else.
 I'll proceed with a patch for this step then.
 
 That will make gdb work better in all the cases where there is
 only one "struct A" in the program.
 
 Michael C


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]