From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20362 invoked by alias); 6 Oct 2008 21:25:47 -0000 Received: (qmail 20354 invoked by uid 22791); 6 Oct 2008 21:25:47 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 06 Oct 2008 21:25:06 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id B77E610D56; Mon, 6 Oct 2008 21:25:04 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id 9AB5B10D34; Mon, 6 Oct 2008 21:25:04 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1KmxZg-0008Ac-5M; Mon, 06 Oct 2008 17:25:04 -0400 Date: Mon, 06 Oct 2008 21:25:00 -0000 From: Daniel Jacobowitz To: Michael Snyder Cc: Joel Brobecker , "gdb-patches@sourceware.org" , Pedro Alves , teawater Subject: Re: [RFA] Reverse Debugging, 1/5 Message-ID: <20081006212504.GB31085@caradoc.them.org> Mail-Followup-To: Michael Snyder , Joel Brobecker , "gdb-patches@sourceware.org" , Pedro Alves , teawater References: <48E3CCB6.4060501@vmware.com> <20081006203021.GA21853@adacore.com> <48EA7C75.7070703@vmware.com> <20081006211131.GA26663@caradoc.them.org> <48EA8065.9070001@vmware.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <48EA8065.9070001@vmware.com> User-Agent: Mutt/1.5.17 (2008-05-11) 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/msg00170.txt.bz2 On Mon, Oct 06, 2008 at 02:17:25PM -0700, Michael Snyder wrote: > You're going to send "to_set_direction" to the target, > and then you're going to assume that you know what the > state is later on, rather than asking the target? What > if the target gets it wrong? Now you're out of sync. Huh? No, part of every resume. > If we do keep the direction-state in the core, where would > we put it? In the ecs? In a global variable in infrun? In infrun, the same as any other user supplied execution state. For instance the scheduler-locking setting. -- Daniel Jacobowitz CodeSourcery