From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4722 invoked by alias); 3 Mar 2010 22:09:26 -0000 Received: (qmail 4713 invoked by uid 22791); 3 Mar 2010 22:09:25 -0000 X-SWARE-Spam-Status: No, hits=-2.7 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS X-Spam-Check-By: sourceware.org Received: from lo.gmane.org (HELO lo.gmane.org) (80.91.229.12) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 03 Mar 2010 22:09:22 +0000 Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1Nmwkp-0004Fj-85 for gdb-patches@sources.redhat.com; Wed, 03 Mar 2010 23:09:19 +0100 Received: from h86-62-88-129.ln.rinet.ru ([86.62.88.129]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 03 Mar 2010 23:09:19 +0100 Received: from vladimir by h86-62-88-129.ln.rinet.ru with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 03 Mar 2010 23:09:19 +0100 To: gdb-patches@sources.redhat.com From: Vladimir Prus Subject: Re: Always disable pagination with MI? Followup-To: gmane.comp.gdb.patches Date: Wed, 03 Mar 2010 22:09:00 -0000 Message-ID: References: <201003032138.54319.pedro@codesourcery.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7Bit User-Agent: KNode/4.3.2 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: 2010-03/txt/msg00135.txt.bz2 Pedro Alves wrote: > A customer noted that sometimes, when GDB failed to evaluate > a watchpoint's condition, GDB would leave the inferior > stopped, but would forget to output a *stopped notification. > Something like this: > > gdb -i=mi ... > ... > (gdb) > &"Error in testing breakpoint condition:\n" > &"Cannot access memory at address 0x0\n" > ~"Hardware watchpoint 2: global2\n" > ~"\n" > > ~"Old value = 1\n" > ~"New value = 2\n" > > And nothing else came out. What was really happening, is > that pagination kicked in at this point, because no pagination > prompt is visible. If one presses enter when this happens, > the rest of the expected output, along with *stopped actually > comes out: ... > Whoops. I tried this on 6.8 and 7.0 and they behave > the same. This was probably never right, and I gather that > most frontends must be disabling pagination > already: either by explicit "set height 0"/"set pagination off", > or implicitly by running GDB from a non-tty, and, those that > want pagination handle it themselves. Yes, I think that's what frontends do. > > Any objections to this? > Seems reasonable, FWIW. - Volodya