From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-28015-listarch-gdb-patches=sources.redhat.com@sources.redhat.com>
Received: (qmail 8572 invoked by alias); 16 Oct 2003 23:24:27 -0000
Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-patches-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sources.redhat.com>
List-Help: <mailto:gdb-patches-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-patches-owner@sources.redhat.com
Received: (qmail 8564 invoked from network); 16 Oct 2003 23:24:27 -0000
Received: from unknown (HELO mx1.redhat.com) (66.187.233.31)
  by sources.redhat.com with SMTP; 16 Oct 2003 23:24:27 -0000
Received: from int-mx2.corp.redhat.com (nat-pool-rdu-dmz.redhat.com [172.16.52.200] (may be forged))
	by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id h9GNOPM12969
	for <gdb-patches@sources.redhat.com>; Thu, 16 Oct 2003 19:24:25 -0400
Received: from potter.sfbay.redhat.com (potter.sfbay.redhat.com [172.16.27.15])
	by int-mx2.corp.redhat.com (8.11.6/8.11.6) with ESMTP id h9GNOJL12791;
	Thu, 16 Oct 2003 19:24:24 -0400
Received: from redhat.com (reddwarf.sfbay.redhat.com [172.16.24.50])
	by potter.sfbay.redhat.com (8.11.6/8.11.6) with ESMTP id h9GNOIJ02399;
	Thu, 16 Oct 2003 16:24:18 -0700
Message-ID: <3F8F28A2.30000@redhat.com>
Date: Thu, 16 Oct 2003 23:24:00 -0000
From: Michael Snyder <msnyder@redhat.com>
Organization: Red Hat, Inc.
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Eli Zaretskii <eliz@elta.co.il>
CC: Andrew Cagney <cagney@gnu.org>, drow@mvista.com,
   gdb-patches@sources.redhat.com
Subject: Re: RFA: Breakpoint infrastructure cleanups [0/8]
References: <20031008165534.GA8718@nevyn.them.org> <vt27k3ffvv5.fsf@zenia.home> <20031008190502.GA13579@nevyn.them.org> <3F846B04.2070801@redhat.com> <3F85B4AC.7000000@redhat.com> <20031014013831.GB6118@nevyn.them.org> <3F8C18DD.3020508@redhat.com> <20031014155126.GA10669@nevyn.them.org> <3F8C605E.1060604@redhat.com> <20031015224134.GA4102@nevyn.them.org> <6654-Thu16Oct2003085007+0200-eliz@elta.co.il> <3F8EAA56.3020900@gnu.org> <7494-Thu16Oct2003175650+0200-eliz@elta.co.il>
In-Reply-To: <7494-Thu16Oct2003175650+0200-eliz@elta.co.il>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-SW-Source: 2003-10/txt/msg00576.txt.bz2

Eli Zaretskii wrote:
>>Date: Thu, 16 Oct 2003 10:25:26 -0400
>>From: Andrew Cagney <cagney@gnu.org>
>>
>>BTW, long term, this stuff is going to be hijacked by other *point 
>>mechanisms.  Variable watchpoints, for instance, will be given a similar 
>>projection (the watchpoint changes that last year stalled can probably 
>>be picked up again).  While the term "breakpoint" may continue to be 
>>used, it will be applied to more than just breakpoints.
> 
> 
> I don't see any problems with that.  In fact, we might wish to start
> educating GDB users to use the term ``breakpoint'' for all of those.
> E.g., many implementations of dbx and other debuggers support
> watchpoints, but call them ``breakpoints'' or ``data breakpoints''.
> Someone whose first debugger was GDB might not even find how to set
> watchpoints unless they try looking for "breakpoint".

The difference between breakpoints and watchpoints may be small,
but the difference between breakpoints and tracepoints is large.
Some people have used the term "stop point".

Other potential stop-points are signals (synch and asynch),
throw and catch, syscalls, longjmp, synchronization, thread
switch, blocking...