From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19714 invoked by alias); 12 Mar 2008 03:13:53 -0000 Received: (qmail 19706 invoked by uid 22791); 12 Mar 2008 03:13:52 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 12 Mar 2008 03:13:33 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 36EB098140; Wed, 12 Mar 2008 03:13:31 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id 07E559811F; Wed, 12 Mar 2008 03:13:30 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1JZHPF-0003Rj-5q; Tue, 11 Mar 2008 23:13:29 -0400 Date: Wed, 12 Mar 2008 03:13:00 -0000 From: Daniel Jacobowitz To: Joel Brobecker Cc: Pedro Alves , gdb-patches@sourceware.org Subject: Re: Don't paginate "new thread" events Message-ID: <20080312031329.GA12967@caradoc.them.org> Mail-Followup-To: Joel Brobecker , Pedro Alves , gdb-patches@sourceware.org References: <200803120149.11929.pedro@codesourcery.com> <20080312030129.GA3738@adacore.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080312030129.GA3738@adacore.com> User-Agent: Mutt/1.5.17 (2007-12-11) X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2008-03/txt/msg00120.txt.bz2 On Tue, Mar 11, 2008 at 08:01:29PM -0700, Joel Brobecker wrote: > > New thread events printing ("New Thread 0x40077950 (LWP 13229)]") was > > recently centralised in add_thread. Unfortunatelly it brought with > > it a behaviour change. Before, we wouldn't paginate when these > > events filled the terminal screen, and now we do. > > Actually, I think it's a little more complicated than that. I had > a second look at the patch, and the routines that were used to print > the event notifications were either "printf_filtered" or "ui_out_text" > (which in CLI mode results in a printf_filtered). The one most frequently encountered, in linux-thread-db.c, was already unfiltered for this very reason. -- Daniel Jacobowitz CodeSourcery