From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16502 invoked by alias); 14 Mar 2002 19:13:40 -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 16425 invoked from network); 14 Mar 2002 19:13:37 -0000 Received: from unknown (HELO taltos.codesourcery.com) (66.92.14.122) by sources.redhat.com with SMTP; 14 Mar 2002 19:13:37 -0000 Received: from zack by taltos.codesourcery.com with local (Exim 3.35 #1 (Debian)) id 16lafR-0005Gs-00 for ; Thu, 14 Mar 2002 11:13:37 -0800 Date: Thu, 14 Mar 2002 11:13:00 -0000 From: Zack Weinberg To: gdb@sources.redhat.com Subject: Re: Suggestion: Detect inconsistent structure definitions Message-ID: <20020314191337.GF19703@codesourcery.com> References: <20020313182221.GE8197@codesourcery.com> <20020313190708.B26841@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020313190708.B26841@nevyn.them.org> User-Agent: Mutt/1.3.27i X-SW-Source: 2002-03/txt/msg00128.txt.bz2 On Wed, Mar 13, 2002 at 07:07:08PM -0500, Daniel Jacobowitz wrote: > > ... When do we have enough information to know that two references > are 'supposed' to be of the same type, rather than an > implementation-private type? And in stabs, at least, no debug > information appears to be emitted for 'extern' statements, so we > don't know if a file referenced the type it had a different > definition of or not. I would argue that this situation is rare, and that most programmers are unlikely to think of incompatible structure definitions as the cause of a bug. Therefore, how about a warning issued by default when the object file is read, but with a way to shut it up per-structure in .gdbinit? > Please file a GNATS PR so that this idea doesn't get forgotten. Done, #420. zw