From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30577 invoked by alias); 21 Oct 2003 21:30:25 -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 30545 invoked from network); 21 Oct 2003 21:30:23 -0000 Received: from unknown (HELO touchme.toronto.redhat.com) (207.219.125.105) by sources.redhat.com with SMTP; 21 Oct 2003 21:30:23 -0000 Received: from redhat.com (toocool.toronto.redhat.com [172.16.14.72]) by touchme.toronto.redhat.com (Postfix) with ESMTP id 4C1E780040B for ; Tue, 21 Oct 2003 17:30:23 -0400 (EDT) Message-ID: <3F95A56F.3090802@redhat.com> Date: Tue, 21 Oct 2003 21:30:00 -0000 From: "J. Johnston" Organization: Red Hat Inc. User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 X-Accept-Language: en-us, en MIME-Version: 1.0 To: gdb@sources.redhat.com Subject: Why does symfile.c use printf_filtered? Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-10/txt/msg00246.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? -- Jeff J.