From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21039 invoked by alias); 24 Oct 2003 18:51:10 -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 21032 invoked from network); 24 Oct 2003 18:51:09 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sources.redhat.com with SMTP; 24 Oct 2003 18:51:09 -0000 Received: from drow by nevyn.them.org with local (Exim 4.24 #1 (Debian)) id 1AD71h-00013P-9s; Fri, 24 Oct 2003 14:51:09 -0400 Date: Fri, 24 Oct 2003 18:51:00 -0000 From: Daniel Jacobowitz To: Andrew Cagney Cc: "J. Johnston" , gdb@sources.redhat.com Subject: Re: Why does symfile.c use printf_filtered? Message-ID: <20031024185109.GA3996@nevyn.them.org> Mail-Followup-To: Andrew Cagney , "J. Johnston" , gdb@sources.redhat.com References: <3F95A56F.3090802@redhat.com> <3F996797.30205@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3F996797.30205@redhat.com> User-Agent: Mutt/1.5.1i X-SW-Source: 2003-10/txt/msg00278.txt.bz2 On Fri, Oct 24, 2003 at 01:55:35PM -0400, Andrew Cagney wrote: > >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. > > > >Would anybody have an objection to me changing to use printf_unfiltered() > >in symfile.c? > > It certainly doesn't look right. Which oesn't look right? > Log messages are there to keep the user up-to-date on what GDB is doing > (and confirm that GDB hasn't hung ...). Just like other such messages > (thread notifications, hosted output from the remote) they should halt "shouldn't"? > GDB and hence shouldn't be paged. > > This is different to something like "info registers" where GDB has > stopped, and the user expects to be able to read the entire response. > > enjoy, > Andrew > > > -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer