From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23083 invoked by alias); 1 Dec 2009 11:32:34 -0000 Received: (qmail 23073 invoked by uid 22791); 1 Dec 2009 11:32:33 -0000 X-SWARE-Spam-Status: No, hits=-0.8 required=5.0 tests=AWL,BAYES_50 X-Spam-Check-By: sourceware.org Received: from vtab.com (HELO oden.vtab.com) (62.20.90.195) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 01 Dec 2009 11:32:23 +0000 Received: from oden.vtab.com (oden.vtab.com [127.0.0.1]) by oden.vtab.com (Postfix) with ESMTP id 6656D26EF17; Tue, 1 Dec 2009 12:32:18 +0100 (CET) Received: from polhem (unknown [62.20.90.206]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by oden.vtab.com (Postfix) with ESMTP id 2EDA226EF2B; Tue, 1 Dec 2009 12:32:18 +0100 (CET) From: "Jakob Engblom" To: "'Sean Chen'" , "'Hui Zhu'" Cc: References: <5e81cb500911262231g57f693dwc885576172e016e1@mail.gmail.com> <5e81cb500911270711wb99d531i111d064f05ef03b4@mail.gmail.com> <5e81cb500911270742j546062f2jca7441a912ffad87@mail.gmail.com> <4B10154F.7070902@vmware.com> <5e81cb500911271745t1a119520l4944919d2139e8ae@mail.gmail.com> <4B11607C.7000500@vmware.com> <5e81cb500911300539r52e8be5dva54d32c734978021@mail.gmail.com> In-Reply-To: <5e81cb500911300539r52e8be5dva54d32c734978021@mail.gmail.com> Subject: RE: System call support in reversible debugging Date: Tue, 01 Dec 2009 11:32:00 -0000 Message-ID: <00a701ca7279$f1a03c60$d4e0b520$@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-12/txt/msg00003.txt.bz2 =20 > Hi Michael and Hui, >=20 > I am sorry for my late response. >=20 > Thanks for your explanation. So we can=92t treat the system calls as a > black box and have to understand the detailed implementation of each > system call. I think we need to understand every lines of the code in > the system calls carefully enough, and care about the difference of > the Linux kernel since the code of system calls might change > frequently. Do we have any good ways to do it? To really do this right, you should use a full-system simulator that lets y= ou debug OS and user code at the same time, as it is attacking the system at t= he hardware/software interface level.=20 As long as you attack a program as a user-level problem only, you cannot de= bug into the kernel, as the process record facilities are built on kernel featu= res that only apply to user-level programs. As I understand it.=20 Both VmWare and Virtutech offer solutions for this that you can drive over gdb-serial, in reverse when needed.=20 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