Re: [RFA] varobj: call CHECK_TYPEDEF

[Daniel Jacobowitz <drow@mvista.com>]

On Thu, Apr 24, 2003 at 10:15:06PM -0400, Andrew Cagney wrote:
> >On Thu, Apr 24, 2003 at 03:29:36PM -0700, Keith Seitz wrote:
> >
> >>On Thu, 2003-04-24 at 15:18, Andrew Cagney wrote:
> >
> >>> BTW, does ...
> >>> 
> >>> struct t
> >>> {
> >>>    int a;
> >>>    int b;
> >>> };
> >>> 
> >>> typedef struct t T;
> >>> 
> >>> main()
> >>> {
> >>>    static T v = {...};
> >>> }
> >>> 
> >>> tickle it?
> >
> >>
> >>Nope, that works properly (except for it being reported as "struct t"
> >>instead of "T").
> >
> >
> >[Keith, you had "test for insight/792" in your posted testsuite patch.]
> >
> >There's at least one compiler bug in this area, where DWARF-2 debug info
> >will say struct t instead of T.  I fixed it for 3.3 and (I think?)
> >3.2.3.  Just in case you start getting confused :)
> 
> So, rather than `bug', `probable gcc bug'?

Depends, I imagine GDB has bugs here too.  Someone should try Keith's
testcase with a fixed GCC I suppose.

(If your compiler has the bug it will show up in the MI testsuite
already; don't remember exactly where.)

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer