From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9764 invoked by alias); 25 Jun 2002 15:40:59 -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 9744 invoked from network); 25 Jun 2002 15:40:55 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by sources.redhat.com with SMTP; 25 Jun 2002 15:40:55 -0000 Received: from cs2876-108.austin.rr.com ([24.28.76.108] helo=branoic) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 17MsR1-0001Km-00; Tue, 25 Jun 2002 10:40:51 -0500 Received: from drow by branoic with local (Exim 3.35 #1 (Debian)) id 17MsQW-0004Yc-00; Tue, 25 Jun 2002 11:40:20 -0400 Date: Tue, 25 Jun 2002 08:40:00 -0000 From: Daniel Jacobowitz To: Peter Barada Cc: Peter.Barada@motorola.com, gdb@sources.redhat.com Subject: Re: Torubles with remote stub for m68k Message-ID: <20020625154020.GA17370@branoic.them.org> Mail-Followup-To: Peter Barada , Peter.Barada@motorola.com, gdb@sources.redhat.com References: <200206242104.g5OL4pY06652@hyper.wm.sps.mot.com> <20020624211258.GA30001@branoic.them.org> <200206242140.g5OLe0L06792@hyper.wm.sps.mot.com> <200206242156.g5OLumH25691@hyper.wm.sps.mot.com> <20020624220628.GB31470@branoic.them.org> <200206251512.g5PFCxZ26374@hyper.wm.sps.mot.com> <20020625151636.GA16694@branoic.them.org> <200206251532.g5PFWao26386@hyper.wm.sps.mot.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200206251532.g5PFWao26386@hyper.wm.sps.mot.com> User-Agent: Mutt/1.3.28i X-SW-Source: 2002-06/txt/msg00247.txt.bz2 On Tue, Jun 25, 2002 at 11:32:36AM -0400, Peter Barada wrote: > > >Terminology skew. "the client" is GDB, not the stub; the stub is > >essentially a server, like gdbserver is. > > Ahh, that makes a bit more sense. > Where in the 'client' does it actually remove the breakpoint? I'll > start debugging gdb to see why that isn't happening... Something like memory_remove_breakpoints, I believe... dig, dig.... via remove_breakpoints (). I believe via the call in infrun.c:normal_stop, but it's been some time. -- Daniel Jacobowitz Carnegie Mellon University MontaVista Software Debian GNU/Linux Developer