From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-13238-listarch-gdb=sources.redhat.com@sources.redhat.com>
Received: (qmail 29466 invoked by alias); 29 Mar 2003 00:49:46 -0000
Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb/>
List-Post: <mailto:gdb@sources.redhat.com>
List-Help: <mailto:gdb-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-owner@sources.redhat.com
Received: (qmail 29459 invoked from network); 29 Mar 2003 00:49:45 -0000
Received: from unknown (HELO localhost.redhat.com) (207.219.125.105)
  by sources.redhat.com with SMTP; 29 Mar 2003 00:49:45 -0000
Received: from redhat.com (localhost [127.0.0.1])
	by localhost.redhat.com (Postfix) with ESMTP
	id 5A2B72B29; Fri, 28 Mar 2003 19:49:42 -0500 (EST)
Message-ID: <3E84EDA6.1040302@redhat.com>
Date: Sat, 29 Mar 2003 00:49:00 -0000
From: Andrew Cagney <ac131313@redhat.com>
User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030223
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Jim Ingham <jingham@apple.com>, gdb@sources.redhat.com
Subject: Re: gdb Digest 26 Mar 2003 19:03:48 -0000 Issue 1129
References: <672C9F08-5FC2-11D7-B2F4-00039379E320@apple.com> <3E84D16F.5020304@redhat.com> <3E84D706.3060708@redhat.com> <20030328235634.GA5920@nevyn.them.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-SW-Source: 2003-03/txt/msg00398.txt.bz2

> Either way, I think these are high-level table entries.  The user could 
>> certainly view the mapping:
>> 
>> maint print breakpoint
>> Breakpoint 1 <template a::foo>FileFullOfTemplates.hh:27 at
>> 0x123 (b.cc:27), 0x234 (b.c:28), ...
>> 
>> but the manipulation would still typically be high level.
> 
> 
> This suggests that we need three levels then.

Not really.

A single user-level breakpoint would have a list of source-code 
locations.  But those source code locations would be tightly bound to 
that single user-level breakpoint.  It is strictly 1:N, not N:N.

Delete the user breakpoint and you delete its list of locations.  The 
source code locations are iterated over when adding/deleting physical 
breakpoints to the lower-level table.

On the other hand.  The user level breakpoint and physical breakpoint 
tables have an N:N relationship.

> Does anyone know how other debuggers handle this?  I'm sure we're not
> the first but it's been ages since I used a non-GDB debugger for
> anything.

The model I'm describing lifted from a book, the author of which was 
involved in borland's debugger.

Andrew