This is the mail archive of the gdb@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: [rfc] debugging anonymous unions


In principle, having the debug info reflect the structure of the code
is a good thing.  But I can't see what it buys us in this case, over
simply emitting all the (effectively) top-level members as separate
variables, whose locations happen to overlap.  Is there anything
interesting you can think of that GDB could do only if it knew there
was an anonymous union involved?


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