From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30756 invoked by alias); 11 Aug 2009 22:43:01 -0000 Mailing-List: contact archer-help@sourceware.org; run by ezmlm Sender: Precedence: bulk List-Post: List-Help: List-Subscribe: List-Id: Received: (qmail 30730 invoked by uid 22791); 11 Aug 2009 22:43:00 -0000 X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org To: Jan Kratochvil Cc: Dodji Seketeli , GDB/Archer list Subject: Re: [RFC] Proposal for a new DWARF name index section References: <4A7FE28D.4050901@redhat.com> <20090810143804.GA8671@host0.dyn.jankratochvil.net> <20090810182136.GA25301@host0.dyn.jankratochvil.net> <4A8123C9.3030209@redhat.com> <20090811174448.GA17263@host0.dyn.jankratochvil.net> From: Tom Tromey Reply-To: Tom Tromey Date: Tue, 11 Aug 2009 22:43:00 -0000 In-Reply-To: <20090811174448.GA17263@host0.dyn.jankratochvil.net> (Jan Kratochvil's message of "Tue\, 11 Aug 2009 19\:44\:48 +0200") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2009-q3/txt/msg00120.txt.bz2 [ time spent reading ] Jan> Most of the time (like >95%, did not measure now), you can try: Yeah, it is the #1 time user and #1 space user :-) I think whatever problems we have here will be exaggerated by multi-exec, too. Dodji> Do global variables and enumerator constants fall into this Dodji> "deprecated" category ? Jan> Global variables are a part of .debug_pubnames and they are not Jan> "deprecated" as they are globally visible in the C language. Jan> enumerator constants are not globally visible, they create no ELF Jan> symbols, they need to be #included for each CU, they are like Jan> static functions, therefore they should not be a part of Jan> .debug_pubnames. Types also are not globally visible and create no ELF symbols. So, I think you need an additional argument about why enum constants ought to be treated differently. Also, I will occasionally start gdb just to "print/d CONSTANT" to see what its value is. So this would be another user-visible change -- we'd require a full debuginfo scan on any expression. (Though it occurs to me that perhaps this is happening due to some "static scope" set at main or something ... I did not check. If so that would eliminate this objection to this particular bit.) Jan> I hope these mails were useful for both sides, at least for me. Me too. Tom