From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1685 invoked by alias); 5 Jan 2011 18:35:25 -0000 Received: (qmail 1576 invoked by uid 22791); 5 Jan 2011 18:35:24 -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, 05 Jan 2011 18:35:17 +0000 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id p05IZEH4031285 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 5 Jan 2011 13:35:14 -0500 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id p05IZDZd022409; Wed, 5 Jan 2011 13:35:13 -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 p05IZCUO012311; Wed, 5 Jan 2011 13:35:13 -0500 Received: by opsy.redhat.com (Postfix, from userid 500) id A05AF37848D; Wed, 5 Jan 2011 11:35:12 -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, 05 Jan 2011 18:35:00 -0000 In-Reply-To: (Doug Evans's message of "Mon, 27 Dec 2010 21:08:29 -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: 2011-01/txt/msg00081.txt.bz2 >>>>> "Doug" == Doug Evans writes: Doug> The user will see the normal breakpoint output, and then be expected Doug> to know that the breakpoint is special (e.g., a rule was violated and Doug> that s/he needs to pay attention to what the rule was). Is there a Doug> plan to have something more? [Or am I missing something?] Yeah, we want to expose some of the breakpoint_ops stuff to python. Doug> Sorry, maybe I was too subtle. Doug> If one is using this facility to implement a rule checker that stops Doug> when the rule is violated, and one sets another breakpoint at the same Doug> location, when the program stops how does one know whether the rule Doug> was violated or not? One does not. This is a pre-existing problem in gdb. Phil, let's withdraw this patch until some later time when we have worked out the issues. We can continue to discuss on the archer list. I think we should at least deal with exposing to Python the bits needed to customize breakpoint notifications. Also we should write a couple real-life uses of this to make sure it is working ok. At least we should update the glibc heap stuff to use it; and if other bits are done in time we can either look at the mutex tracker (requires Sergio's work) or return breakpoints (I think this requires Sami's work). Tom