Re: [rfa] lookup_transparent_type hack

[Daniel Jacobowitz <drow at mvista dot com>]

On Fri, Jan 23, 2004 at 03:06:45PM -0800, David Carlton wrote:
> On Thu, 22 Jan 2004 14:00:08 -0800, David Carlton <carlton@kealia.com> said:
> 
> > These failures aren't caused by my patch to GDB - they happen with or
> > without the patch - but I want to look into the reason for the
> > behavior first before committing the patch.
> 
> I've looked into them; as I suspected, they didn't really have
> anything to do with this patch.  There is a bug in the way I handle
> the debug output that GCC 3.4 generates for classes in namespaces;
> I'll submit a patch for that later this afternoon.  And, once I fixed
> that bug, I discovered that, if you do:
> 
> 
>   void func ()
>   {
>     C2 *obj = create2 ();
> 
>     return;
>   }
> 
> and set a breakpoint on the 'return' line then, if it's compiled with
> GCC 3.4, 'print *obj' claims that there isn't a variable named 'obj'.
> Sigh.

Yes, there are a number of these in our testsuite - and I think that
GCC is not at fault.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer