From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26812 invoked by alias); 23 Oct 2003 19:34:18 -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 26804 invoked from network); 23 Oct 2003 19:34:18 -0000 Received: from unknown (HELO zenia.home) (12.223.225.216) by sources.redhat.com with SMTP; 23 Oct 2003 19:34:18 -0000 Received: by zenia.home (Postfix, from userid 5433) id 07B4620766; Thu, 23 Oct 2003 14:33:59 -0500 (EST) To: Jim Ingham Cc: gdb@sources.redhat.com, Jeff Johnston Subject: Re: Why does symfile.c use printf_filtered? References: <1066860856.12586.ezmlm@sources.redhat.com> <77974AB1-04E8-11D8-A22C-000A958F4C44@apple.com> From: Jim Blandy Date: Thu, 23 Oct 2003 19:34:00 -0000 In-Reply-To: <77974AB1-04E8-11D8-A22C-000A958F4C44@apple.com> 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-10/txt/msg00267.txt.bz2 Jim Ingham writes: > These messages only show up when you set verbose on, so they don't > appear in the normal case. Then I think you just get one dot per > shared library. No, that's not right: symfile.c:symbol_file_add_with_addrs_or_offsets: if ((objfile->flags & OBJF_MAPPED) && (objfile->flags & OBJF_SYMS)) ... else { /* We either created a new mapped symbol table, mapped an existing symbol table file which has not had initial symbol reading performed, or need to read an unmapped symbol table. */ if (from_tty || info_verbose) { if (pre_add_symbol_hook) pre_add_symbol_hook (name); else { printf_filtered ("Reading symbols from %s...", name); wrap_here (""); gdb_flush (gdb_stdout); } } syms_from_objfile (objfile, addrs, offsets, num_offsets, mainline, from_tty); } So it shows up when invoked from a command, too. And I don't see any "dot per shared library code" here --- perhaps that's a local mod. Perhaps the best behavior would be for GDB to print a dot per shlib, unless 'set verbose on' is on, in which case it should print the full filename. Jeff, how does that sound? Is that more trouble than you wanted to get into, or would you be willing to put together a patch for that?