From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7431 invoked by alias); 16 Apr 2002 05:47:11 -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 7397 invoked from network); 16 Apr 2002 05:47:09 -0000 Received: from unknown (HELO localhost.redhat.com) (24.112.240.27) by sources.redhat.com with SMTP; 16 Apr 2002 05:47:09 -0000 Received: from cygnus.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 61D0F3C71; Tue, 16 Apr 2002 01:47:17 -0400 (EDT) Message-ID: <3CBBBAE5.8030601@cygnus.com> Date: Mon, 15 Apr 2002 22:47:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:0.9.9) Gecko/20020328 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel Jacobowitz Cc: gdb-patches@sources.redhat.com Subject: Re: PATCH: breakpoints for gdbserver References: <20020416013218.A1180@nevyn.them.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-04/txt/msg00550.txt.bz2 > 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''? Andrew