From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23938 invoked by alias); 26 Apr 2013 20:30:29 -0000 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 Received: (qmail 23928 invoked by uid 89); 26 Apr 2013 20:30:29 -0000 X-Spam-SWARE-Status: No, score=-6.4 required=5.0 tests=AWL,BAYES_00,RCVD_IN_HOSTKARMA_W,RCVD_IN_HOSTKARMA_WL,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.1 Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Fri, 26 Apr 2013 20:30:28 +0000 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r3QKUK9C016948 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 26 Apr 2013 16:30:26 -0400 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id r3QKU3x9008849 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Fri, 26 Apr 2013 16:30:10 -0400 From: Tom Tromey To: Hui Zhu Cc: gdb-patches ml Subject: Re: [PATCH] not trigger pagination with dprintf References: <87zjwuv0qn.fsf@fleche.redhat.com> <87li87ll0r.fsf@fleche.redhat.com> Date: Sat, 27 Apr 2013 11:40:00 -0000 In-Reply-To: (Hui Zhu's message of "Fri, 26 Apr 2013 11:35:02 +0800") Message-ID: <87fvyd827o.fsf@fleche.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-SW-Source: 2013-04/txt/msg00832.txt.bz2 Hui> Because as the Marc said in bugzilla, when pagination is triggered, Hui> inferior execution will be interrupted until the user answers the Hui> pagination prompt. And dptintf breakpoint call printf in its Hui> commands. So I want to make dprintf can handle it. If pagination from a breakpoint's commands really breaks gdb, then it should be disabled universally while in "commands", not just for dprintf. If it doesn't break gdb, well, then it seems like it is what the user asked for. Tom