From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23547 invoked by alias); 24 Oct 2003 20:50:28 -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 23533 invoked from network); 24 Oct 2003 20:50:28 -0000 Received: from unknown (HELO localhost.redhat.com) (207.219.125.105) by sources.redhat.com with SMTP; 24 Oct 2003 20:50:28 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 2C68F2B89; Fri, 24 Oct 2003 16:50:29 -0400 (EDT) Message-ID: <3F999095.8050807@redhat.com> Date: Fri, 24 Oct 2003 20:50: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: Daniel Jacobowitz Cc: Andrew Cagney , "J. Johnston" , gdb@sources.redhat.com Subject: Re: Why does symfile.c use printf_filtered? References: <3F95A56F.3090802@redhat.com> <3F996797.30205@redhat.com> <20031024185109.GA3996@nevyn.them.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-10/txt/msg00280.txt.bz2 > 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"? Grr, yes. "shouldn't". Having the hosted output, fir instance, stop after 24 lines would (and did) drive people batty :-) >> 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. .