From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-77158-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 31936 invoked by alias); 22 Dec 2010 15:58:36 -0000
Received: (qmail 31926 invoked by uid 22791); 22 Dec 2010 15:58:34 -0000
X-SWARE-Spam-Status: No, hits=-2.6 required=5.0	tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,SPF_HELO_PASS,T_RP_MATCHES_RCVD
X-Spam-Check-By: sourceware.org
Received: from smtp-out.google.com (HELO smtp-out.google.com) (74.125.121.67)    by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 22 Dec 2010 15:58:29 +0000
Received: from wpaz33.hot.corp.google.com (wpaz33.hot.corp.google.com [172.24.198.97])	by smtp-out.google.com with ESMTP id oBMFwQcr021152	for <gdb-patches@sourceware.org>; Wed, 22 Dec 2010 07:58:27 -0800
Received: from qwg5 (qwg5.prod.google.com [10.241.194.133])	by wpaz33.hot.corp.google.com with ESMTP id oBMFsP6J027340	for <gdb-patches@sourceware.org>; Wed, 22 Dec 2010 07:58:25 -0800
Received: by qwg5 with SMTP id 5so4919130qwg.34        for <gdb-patches@sourceware.org>; Wed, 22 Dec 2010 07:58:25 -0800 (PST)
MIME-Version: 1.0
Received: by 10.224.11.17 with SMTP id r17mr6551862qar.304.1293033505094; Wed, 22 Dec 2010 07:58:25 -0800 (PST)
Received: by 10.220.60.10 with HTTP; Wed, 22 Dec 2010 07:58:25 -0800 (PST)
In-Reply-To: <m3fwtq51zj.fsf@fleche.redhat.com>
References: <m38vztlr2r.fsf@redhat.com>	<AANLkTimS_32d+7phemj95qCSdJzgXXOxjMhbt_9+i8D6@mail.gmail.com>	<m34oags1q1.fsf@fleche.redhat.com>	<AANLkTimVN=3CKL2VmKWERSmGxiMA7wDv7pMrSQZc1DMO@mail.gmail.com>	<m3ipyulpop.fsf@fleche.redhat.com>	<AANLkTim_wXWA2OX1GdZ_rFVwBAr+YjO+B5SSVUN_g0vK@mail.gmail.com>	<m3fwtq51zj.fsf@fleche.redhat.com>
Date: Wed, 22 Dec 2010 16:34:00 -0000
Message-ID: <AANLkTikk03p4m+s0k+UD8RRVy8YL7wYZsLhy2GNc6d8q@mail.gmail.com>
Subject: Re: [patch] Add an evaluation function hook to Python breakpoints.
From: Doug Evans <dje@google.com>
To: Tom Tromey <tromey@redhat.com>
Cc: pmuldoon@redhat.com, gdb-patches@sourceware.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-System-Of-Record: true
X-IsSubscribed: yes
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-patches.sourceware.org>
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
X-SW-Source: 2010-12/txt/msg00403.txt.bz2

On Tue, Dec 21, 2010 at 12:01 PM, Tom Tromey <tromey@redhat.com> wrote:
>>>>>> "Doug" =3D=3D Doug Evans <dje@google.com> writes:
>
> Doug> For example, what happens after a checker employing stop_p says
> Doug> "stop"? =A0There's nothing more in the API that helps the user know
> Doug> *why* the checker said "stop". =A0At the moment the API doesn't pro=
vide
> Doug> anything. =A0Checkers will have to print an error message, but I ha=
ve 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. =A0So, if
> it requests a stop, it will be reported as coming from that breakpoint.

That feels a bit subtle (and easy for the user to confuse with a
normal breakpoint).
[e.g. as compared to getting a SIGSEGV]

Plus will it also breakdown if a developer sets his/her own breakpoint
at that location?