From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16060 invoked by alias); 24 Oct 2003 17:55:34 -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 16041 invoked from network); 24 Oct 2003 17:55:34 -0000 Received: from unknown (HELO localhost.redhat.com) (207.219.125.105) by sources.redhat.com with SMTP; 24 Oct 2003 17:55:34 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 3880A2B89; Fri, 24 Oct 2003 13:55:35 -0400 (EDT) Message-ID: <3F996797.30205@redhat.com> Date: Fri, 24 Oct 2003 17:55:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030820 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "J. Johnston" Cc: gdb@sources.redhat.com Subject: Re: Why does symfile.c use printf_filtered? References: <3F95A56F.3090802@redhat.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-10/txt/msg00277.txt.bz2 > 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. 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 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