From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26410 invoked by alias); 12 Feb 2003 20:49:18 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 26403 invoked from network); 12 Feb 2003 20:49:17 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by 172.16.49.205 with SMTP; 12 Feb 2003 20:49:17 -0000 Received: from nevyn.them.org ([66.93.61.169] ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 18j5hp-0004Uo-00 for ; Wed, 12 Feb 2003 16:50:17 -0600 Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian)) id 18j3oh-0000AO-00 for ; Wed, 12 Feb 2003 15:49:15 -0500 Date: Wed, 12 Feb 2003 20:49:00 -0000 From: Daniel Jacobowitz To: gdb Subject: Re: ARM7, remote GDB, Software Breakpoints Message-ID: <20030212204915.GA575@nevyn.them.org> Mail-Followup-To: gdb References: <200302122117.58218.tmohr@s.netic.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200302122117.58218.tmohr@s.netic.de> User-Agent: Mutt/1.5.1i X-SW-Source: 2003-02/txt/msg00204.txt.bz2 On Wed, Feb 12, 2003 at 09:17:58PM +0100, Torsten Mohr wrote: > Hi, > > thanks for your hint. > > > > 1. I could handle HW breakpoints, how can i tell GDB that it should > > > use HW breakpoints? Just answering requests for SW breakpoints with > > > "ENN" doesn't seem to make GDB use HW breakpoints. > > > > You have to implement commands starting with 'Z' and 'z' in order to > > support hw breakpoints. > > Yes, i do that. According to GDB remote protocol, when i answer > a request for "Z0..." with "ENN" (means "i can't handle software > breakpoints"), GDB doesn't try hardware breakpoints. > > But maybe, when i have some hardware that doesn't run in RAM, > but in Flash-ROM, i think i'd rather like to have HW breakpoints. > Also, when i don't answer with "ENN", but with "" (empty), > GDB doesn't try HW breakpoints. This was touched recently. The remote logic decides that 0 hardware breakpoint resources are available; I don't remember if the patch to fix it was checked in. You might want to ask Andrew if he remembers the problem. There's probably something in the host gdb you have to set. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer