From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1986 invoked by alias); 21 Dec 2010 20:02:04 -0000 Received: (qmail 1967 invoked by uid 22791); 21 Dec 2010 20:02:02 -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; Tue, 21 Dec 2010 20:01:58 +0000 Received: from int-mx02.intmail.prod.int.phx2.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id oBLK1r1N028334 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 21 Dec 2010 15:01:53 -0500 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx02.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id oBLK1rmM012130; Tue, 21 Dec 2010 15:01:53 -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 oBLK1qE6006813; Tue, 21 Dec 2010 15:01:52 -0500 Received: by opsy.redhat.com (Postfix, from userid 500) id 37535378493; Tue, 21 Dec 2010 13:01:52 -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: Tue, 21 Dec 2010 20:02:00 -0000 In-Reply-To: (Doug Evans's message of "Tue, 21 Dec 2010 09:33:26 -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=us-ascii 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/msg00384.txt.bz2 >>>>> "Doug" == Doug Evans writes: Doug> For example, what happens after a checker employing stop_p says Doug> "stop"? There's nothing more in the API that helps the user know Doug> *why* the checker said "stop". At the moment the API doesn't provide Doug> anything. Checkers will have to print an error message, but I have a Doug> feeling something more will be useful. Doug> [Did you have something in mind, or am I missing something?] The method in question is attached to a particular breakpoint. So, if it requests a stop, it will be reported as coming from that breakpoint. This falls down a little if the breakpoint is internal. For this I think we will need to export a breakpoint_ops method to python. Tom