From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8133 invoked by alias); 22 Dec 2010 16:20:09 -0000 Received: (qmail 8110 invoked by uid 22791); 22 Dec 2010 16:20:04 -0000 X-SWARE-Spam-Status: No, hits=-6.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,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, 22 Dec 2010 16:19:59 +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.13.8/8.13.8) with ESMTP id oBMGJsIV005120 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 22 Dec 2010 11:19:55 -0500 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id oBMGJsLQ012016; Wed, 22 Dec 2010 11:19:54 -0500 Received: from opsy.redhat.com (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id oBMGJlPY027106; Wed, 22 Dec 2010 11:19:51 -0500 Received: by opsy.redhat.com (Postfix, from userid 500) id 058BBC8814F; Wed, 22 Dec 2010 09:19:46 -0700 (MST) From: Tom Tromey To: Doug Evans Cc: pmuldoon@redhat.com, gdb-patches@sourceware.org Subject: Re: [patch] Add an evaluation function hook to Python breakpoints. References: Date: Wed, 22 Dec 2010 17:35:00 -0000 In-Reply-To: (Doug Evans's message of "Wed, 22 Dec 2010 07:58:25 -0800") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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-12/txt/msg00404.txt.bz2 >>>>> "Doug" =3D=3D Doug Evans writes: >> The method in question is attached to a particular breakpoint. =C2=A0So,= if >> it requests a stop, it will be reported as coming from that breakpoint. Doug> That feels a bit subtle (and easy for the user to confuse with a Doug> normal breakpoint). But it will actually be a normal breakpoint. Doug> Plus will it also breakdown if a developer sets his/her own breakpoint Doug> at that location? No, it will continue to do the right thing. In fact that is one of the major points of this patch, see the requirements upthread. Tom