From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24325 invoked by alias); 30 Nov 2003 02:48:27 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 24298 invoked from network); 30 Nov 2003 02:48:26 -0000 Received: from unknown (HELO zenia.home) (12.223.225.216) by sources.redhat.com with SMTP; 30 Nov 2003 02:48:26 -0000 Received: by zenia.home (Postfix, from userid 5433) id ABE6420766; Sat, 29 Nov 2003 21:47:28 -0500 (EST) To: Richard Henderson Cc: gcc@gcc.gnu.org, gdb@gcc.gnu.org Subject: Re: [rfc] debugging anonymous unions References: <20031128215759.GA31439@twiddle.net> From: Jim Blandy Date: Sun, 30 Nov 2003 02:48:00 -0000 In-Reply-To: <20031128215759.GA31439@twiddle.net> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-11/txt/msg00296.txt.bz2 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?