From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21327 invoked by alias); 22 Oct 2003 13:30:41 -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 21319 invoked from network); 22 Oct 2003 13:30:39 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sources.redhat.com with SMTP; 22 Oct 2003 13:30:39 -0000 Received: from drow by nevyn.them.org with local (Exim 4.24 #1 (Debian)) id 1ACJ4Q-0005J5-Ng for ; Wed, 22 Oct 2003 09:30:38 -0400 Date: Wed, 22 Oct 2003 13:30:00 -0000 From: Daniel Jacobowitz To: gdb@sources.redhat.com Subject: Re: Why does symfile.c use printf_filtered? Message-ID: <20031022133038.GA20323@nevyn.them.org> Mail-Followup-To: gdb@sources.redhat.com References: <3F95A56F.3090802@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.1i X-SW-Source: 2003-10/txt/msg00250.txt.bz2 On Wed, Oct 22, 2003 at 08:17:22AM +0200, Eli Zaretskii wrote: > > Date: Tue, 21 Oct 2003 17:30:23 -0400 > > From: "J. Johnston" > > > > Does anybody know why symfile.c uses printf_filtered()? > > > > This causes a couple of problems, most notably when you load a module with a lot > > of shared library references. The messages for "Reading symbols from"... inside > > symfile.c are printed filtered so eventually we end up causing a page break. I > > do not think this information is worthy of requiring user intervention. > > Unless there's some important situation where this is necessary, it > does seem silly to use printf_filtered in this case. Very strongly agree. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer