From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9181 invoked by alias); 22 Oct 2003 06:16:29 -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 9166 invoked from network); 22 Oct 2003 06:16:27 -0000 Received: from unknown (HELO monty-python.gnu.org) (199.232.76.173) by sources.redhat.com with SMTP; 22 Oct 2003 06:16:27 -0000 Received: from [207.232.27.5] (helo=WST0054) by monty-python.gnu.org with asmtp (Exim 4.24) id 1ACCHP-0000vf-BM; Wed, 22 Oct 2003 02:15:41 -0400 Date: Wed, 22 Oct 2003 06:16:00 -0000 Message-Id: From: Eli Zaretskii To: "J. Johnston" CC: gdb@sources.redhat.com In-reply-to: <3F95A56F.3090802@redhat.com> (jjohnstn@redhat.com) Subject: Re: Why does symfile.c use printf_filtered? Reply-to: Eli Zaretskii References: <3F95A56F.3090802@redhat.com> X-SW-Source: 2003-10/txt/msg00247.txt.bz2 > 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.