From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19270 invoked by alias); 19 Oct 2003 15:55:20 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 19263 invoked from network); 19 Oct 2003 15:55:19 -0000 Received: from unknown (HELO localhost.redhat.com) (65.49.0.121) by sources.redhat.com with SMTP; 19 Oct 2003 15:55:19 -0000 Received: from gnu.org (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 257902B89; Sun, 19 Oct 2003 11:55:18 -0400 (EDT) Message-ID: <3F92B3E5.8010209@gnu.org> Date: Sun, 19 Oct 2003 15:55:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030820 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel Jacobowitz , Michael Snyder Cc: gdb-patches@sources.redhat.com Subject: Re: RFA: Breakpoint infrastructure cleanups [0/8] References: <20031008165534.GA8718@nevyn.them.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-10/txt/msg00609.txt.bz2 > This will make it simpler to have, for instance, a breakpoint on both the > in-charge and not-in-charge constructors without bothering the user with > that detail. Similarly (eventually!) for copies of an inlined function, or > multiple copies of an executed line. This is a bit of a ways in the future > but I'm working on it. I get the feeling that the naming discussion has converged to: "breakpoint" and "location" where a breakpoint has 1:N locations, and multiple breakpoints can share common locations. Unlike the "user" vs "machine" I don't see us having much difficulty explaining "breakpoint" and "location" to either users or developers. Ya! enjoy, Andrew