From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12007 invoked by alias); 16 Apr 2002 14:35:12 -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 11999 invoked from network); 16 Apr 2002 14:35:08 -0000 Received: from unknown (HELO nevyn.them.org) (128.2.145.6) by sources.redhat.com with SMTP; 16 Apr 2002 14:35:08 -0000 Received: from drow by nevyn.them.org with local (Exim 3.35 #1 (Debian)) id 16xU3M-00056D-00; Tue, 16 Apr 2002 10:35:28 -0400 Date: Tue, 16 Apr 2002 07:35:00 -0000 From: Daniel Jacobowitz To: Andrew Cagney Cc: gdb-patches@sources.redhat.com Subject: Re: PATCH: breakpoints for gdbserver Message-ID: <20020416103528.A19474@nevyn.them.org> Mail-Followup-To: Andrew Cagney , gdb-patches@sources.redhat.com References: <20020416013218.A1180@nevyn.them.org> <3CBBBAE5.8030601@cygnus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3CBBBAE5.8030601@cygnus.com> User-Agent: Mutt/1.3.23i X-SW-Source: 2002-04/txt/msg00553.txt.bz2 On Tue, Apr 16, 2002 at 01:47:17AM -0400, Andrew Cagney wrote: > >This gives gdbserver a framework for memory-shadowing breakpoints, > >invisible > >to GDB. They won't behave gracefully if GDB tries to single-step over them > >or if the user puts breakpoints at the same places; I intend to control all > >the cases where gdbserver might insert them with command line options, so > >that if (say) you want to debug LinuxThreads, you can turn off gdbserver > >thread support. That's the only way to get reasonable results, IMHO. > > Um, what exactly do you mean by ``memory-shadowing breakpoints''? Sorry - breakpoints which overwrite an instruction, but keep a shadow buffer so that GDB can't even tell they are there. Pretty standard software breakpoints, really. -- Daniel Jacobowitz Carnegie Mellon University MontaVista Software Debian GNU/Linux Developer