From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12831 invoked by alias); 13 Jun 2011 02:03:03 -0000 Received: (qmail 12788 invoked by uid 22791); 13 Jun 2011 02:03:00 -0000 X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST X-Spam-Check-By: sourceware.org Received: from mail-pv0-f169.google.com (HELO mail-pv0-f169.google.com) (74.125.83.169) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 13 Jun 2011 02:02:45 +0000 Received: by pvc12 with SMTP id 12so2293503pvc.0 for ; Sun, 12 Jun 2011 19:02:44 -0700 (PDT) Received: by 10.142.188.21 with SMTP id l21mr751478wff.258.1307930564740; Sun, 12 Jun 2011 19:02:44 -0700 (PDT) Received: from [10.5.0.40] ([159.226.43.45]) by mx.google.com with ESMTPS id d15sm5461035wfl.18.2011.06.12.19.02.42 (version=SSLv3 cipher=OTHER); Sun, 12 Jun 2011 19:02:43 -0700 (PDT) Message-ID: <4DF56F5D.2090000@gmail.com> Date: Mon, 13 Jun 2011 02:03:00 -0000 From: pi3orama User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110518 Lightning/1.0b3pre Thunderbird/3.1.10 MIME-Version: 1.0 To: Robert Bu CC: gdb@sourceware.org Subject: Re: ReBranch - a record-replay debugging tool References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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: 2011-06/txt/msg00089.txt.bz2 Yes, you are right. (P.S: On the perspective of user processes, all IO interactions are come from system calls, so for single thread processes, most of the time recording system calls is enough for data-flow. The only exception I have seen is vmsplice(): it temporary makes shared memory between 2 processes.) > Hi, > > For data flow, recording syscall is not enough. There may be IO interaction. > I think your current implementation looks like a PC tracing, replaying tool. > > Robert > >> From: pi3orama >> To: paawan oza >> Date: Fri, 10 Jun 2011 17:34:23 +0800 >> Subject: Re: ReBranch - a record-replay debugging tool >> In multi-thread situation, nearly all data-flow information is lost >> because of propagation. However, in single thread situation, signal >> processing and system call results are all recorded and replayed, all >> data-flow info can still be restored. >> >>> ok got that point. >>> so in conclusion, any data-flow info which is reponsible for crash may not be >>> caught by rebranch, or there is a way ? >>> >>> Regards, >>> Oza.