From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23245 invoked by alias); 16 May 2012 21:06:43 -0000 Received: (qmail 23233 invoked by uid 22791); 16 May 2012 21:06:43 -0000 X-SWARE-Spam-Status: No, hits=-6.5 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,RCVD_IN_DNSWL_HI,RCVD_IN_HOSTKARMA_W,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 16 May 2012 21:06:30 +0000 Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q4GL6S42014329 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 16 May 2012 17:06:28 -0400 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id q4GL6RG6026286 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 16 May 2012 17:06:28 -0400 From: Tom Tromey To: Stan Shebs Cc: gdb-patches@sourceware.org Subject: Re: [PATCH v2] dynamic printf References: <4FA8BC97.2000801@earthlink.net> <4FA8D049.109@codesourcery.com> <4FB12A8E.7040905@earthlink.net> <87ipfvop8i.fsf@fleche.redhat.com> <4FB41216.2080508@earthlink.net> Date: Wed, 16 May 2012 21:06:00 -0000 In-Reply-To: <4FB41216.2080508@earthlink.net> (Stan Shebs's message of "Wed, 16 May 2012 13:46:14 -0700") Message-ID: <87aa17n8do.fsf@fleche.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.95 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain 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: 2012-05/txt/msg00637.txt.bz2 >>>>> "Stan" == Stan Shebs writes: Tom> I thought this approach would break "next"ing over a dprintf location. Stan> Indeed, thus this part of the introduction to this patch: :-) I you read the binutils list today you'll see I'm quite off my game. Sorry about the poor reading comprehension. Stan> "... Joel previously noted a problem with the "continue" in the Stan> command list, which is that stepping/nexting over a dprintf becomes a Stan> continue instead (this is a problem for general breakpoint command Stan> lists as well). I tinkered with bpstats a bit, but didn't come up Stan> with a good solution. One possibility might be a new pseudo-command Stan> for breakpoint command lists, that resumes the program using the same Stan> proceed() arguments as the command that caused the breakpoint hit." Yeah, we added the 'stop' machinery to Python to let us deal with this. One idea would be "continue -hey-dont-break-next" Stan> If nobody comes up with a good idea here, it should probably be Stan> documented as a limitation. I wonder if some relatively recent infrun Stan> tinkering changed the breakpoint command behavior - you'd think Stan> *somebody* would have bumped into it sometime in the past 20 years... I've known about it for a long time, I think we all just worked around it. Tom