From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10515 invoked by alias); 17 Oct 2008 14:48:55 -0000 Received: (qmail 10504 invoked by uid 22791); 17 Oct 2008 14:48:52 -0000 X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 17 Oct 2008 14:48:16 +0000 Received: (qmail 31927 invoked from network); 17 Oct 2008 14:48:14 -0000 Received: from unknown (HELO orlando.local) (pedro@127.0.0.2) by mail.codesourcery.com with ESMTPA; 17 Oct 2008 14:48:14 -0000 From: Pedro Alves To: Michael Snyder Subject: Re: [RFA] Displaced stepping just enable in non-stop mode Date: Fri, 17 Oct 2008 14:48:00 -0000 User-Agent: KMail/1.9.9 Cc: Eli Zaretskii , teawater@gmail.com, gdb-patches@sourceware.org, brobecker@adacore.com References: <20081016183217.GA27176@caradoc.them.org> <48F7AEF2.4050405@vmware.com> In-Reply-To: <48F7AEF2.4050405@vmware.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200810171548.12752.pedro@codesourcery.com> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2008-10/txt/msg00429.txt.bz2 On Thursday 16 October 2008 22:15:30, Michael Snyder wrote: > What it looks like is that you try to write to memory > that's write-protected. > > This is because most replay targets will treat all of memory > as write-protected when they are in replay mode. > > Where this usually manifests is, you'll say "continue" > (probably for the first time since attaching to the target), > and it'll croak because it's trying to step over some > "invisible" breakpoint such as the one that handles > shared libraries. I see, then this means that all the reverse targets in existance implement inserting breakpoints (target_insert_breakpoint, Z packet), instead of relying on memory breakpoints. Ah, the record target just ignores breakpoint insertions, and relies on forcing single-stepping and checking breakpoint hits itself. -- Pedro Alves