From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11501 invoked by alias); 4 Mar 2006 15:05:19 -0000 Received: (qmail 11492 invoked by uid 22791); 4 Mar 2006 15:05:18 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Sat, 04 Mar 2006 15:05:17 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1FFYJn-0005YI-Dz for gdb-patches@sourceware.org; Sat, 04 Mar 2006 10:05:15 -0500 Date: Sat, 04 Mar 2006 15:11:00 -0000 From: Daniel Jacobowitz To: gdb-patches@sourceware.org Subject: Re: Save the length of inserted breakpoints Message-ID: <20060304150514.GC20187@nevyn.them.org> Mail-Followup-To: gdb-patches@sourceware.org References: <20060303141123.GA8069@nevyn.them.org> <20060303175407.GA14450@nevyn.them.org> <20060303214359.GA20872@nevyn.them.org> <20060303221003.GA21606@nevyn.them.org> <20060304144330.GA20187@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.8i X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2006-03/txt/msg00099.txt.bz2 On Sat, Mar 04, 2006 at 04:54:04PM +0200, Eli Zaretskii wrote: > > Date: Sat, 4 Mar 2006 09:43:30 -0500 > > From: Daniel Jacobowitz > > > > > > There's a division in GDB between the target, which is a method of > > > > communication et cetera ("how"), and the architecture, which describes > > > > "what" is being debugged. > > > > > > Btw, is this division described anywhere? > > > > Yes, extensively, in gdbint. > > I looked there before asking, so please tell what is the section name > that describes this. Sorry for being blind. They have their own chapters: Target Architecture Definition and Target Vector Definition. Perhaps the titles could be clarified. GDB's target architecture defines what sort of machine-language programs GDB can work with, and how it works with them. versus The target vector defines the interface between GDB's abstract handling of target systems, and the nitty-gritty code that actually exercises control over a process or a serial port. > > The CPSR support is turning out to be a remarkable pain for such a > > simple change. > > That's why I thought we should discuss the design aspects here. Do you have any suggestions for the design? Mark suggested a more symmetric interface, which I agreed to implement. You suggested not modifying the interface and instead having targets keep track. I've tried to explain why I don't think that's a good idea, but if you aren't convinced, I'll do it that way instead. Heh... another way I could make the interface more symmetric would be to bump up the size of the shadow contents vector, and have targets which care about the size store the length in there when inserting the breakpoint. -- Daniel Jacobowitz CodeSourcery