From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19079 invoked by alias); 26 Oct 2009 08:06:34 -0000 Received: (qmail 19068 invoked by uid 22791); 26 Oct 2009 08:06:33 -0000 X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from dns.vtab.com (HELO oden.vtab.com) (62.20.90.195) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 26 Oct 2009 08:06:28 +0000 Received: from oden.vtab.com (oden.vtab.com [127.0.0.1]) by oden.vtab.com (Postfix) with ESMTP id 3407726EF0E for ; Mon, 26 Oct 2009 09:06:26 +0100 (CET) Received: from polhem (c83-253-31-27.bredband.comhem.se [83.253.31.27]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by oden.vtab.com (Postfix) with ESMTP id 0DD5D26EEDD for ; Mon, 26 Oct 2009 09:06:26 +0100 (CET) From: "Jakob Engblom" To: References: <4ADA4BD8.6080800@vmware.com> <4ADCAD14.3080407@vmware.com> <4ADE1824.8090701@vmware.com> <4ADE2502.5060201@undo-software.com> In-Reply-To: Subject: RE: [FYI] tutorial for process record and reverse debugging Date: Mon, 26 Oct 2009 09:59:00 -0000 Message-ID: <00a501ca5613$37d69ea0$a783dbe0$@com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2009-10/txt/msg00374.txt.bz2 > > FWIW, early versions of UndoDB operated in "Marc-mode". We > > changed it > > because replay mode and record are quite different, > > particularly w.r.t. > > to the program's interaction with the outside world. "Silent" > > transition > > from replay to record mode could be quite confusing/surprising. >=20 > In cases where the program does interact with the outside world, > I agree that "auto-mode" could be confusing. In fact, "record mode" > may not be the one we want in this case either. For instance, in > some cases I may want to re-execute instructions that affect the outside > world, even if I'm gone backwards. In this case I would want to use > the recorded data to go backwards, but never to go forward (never use > "replay mode"). Well, it actually can be made to work: * Make sure the target is isolated, and that the debugger system can catch anything going to the outside. This is trivial in a simulator or VM. * When working with past time, don't send on things to the outside world. T= his means reverse, replay, and going back again. * When in progression forward, do connect to the outside world. The only pr= oblem here are time-outs.=20 Obviously, my favorite solution is to just get around the entire problem by including a sufficient component of the world inside the reversible system, inside a system simulator. Best regards, /jakob _______________________________________________________ Jakob Engblom, PhD, Technical Marketing Manager Virtutech=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Direct: +46= 8 690 07 47=A0=A0=A0 Drottningholmsv=E4gen 22=A0=A0=A0=A0=A0 Mobile: +46 709 242 646=A0=A0 11243 Stockholm=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Web:=A0=A0=A0 www.virtu= tech.com=A0 Sweden ________________________________________________________ =A0=20