From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28205 invoked by alias); 6 Apr 2009 20:03:46 -0000 Received: (qmail 27245 invoked by uid 22791); 6 Apr 2009 20:03:40 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from smtp-outbound-2.vmware.com (HELO smtp-outbound-2.vmware.com) (65.115.85.73) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 06 Apr 2009 20:03:34 +0000 Received: from mailhost2.vmware.com (mailhost2.vmware.com [10.16.67.167]) by smtp-outbound-2.vmware.com (Postfix) with ESMTP id 2E9F73A00C; Mon, 6 Apr 2009 13:03:27 -0700 (PDT) Received: from [10.20.94.141] (msnyder-server.eng.vmware.com [10.20.94.141]) by mailhost2.vmware.com (Postfix) with ESMTP id 173A38E647; Mon, 6 Apr 2009 13:03:27 -0700 (PDT) Message-ID: <49DA5F4F.9070007@vmware.com> Date: Mon, 06 Apr 2009 20:10:00 -0000 From: Michael Snyder User-Agent: Thunderbird 1.5.0.12 (X11/20080411) MIME-Version: 1.0 To: Zhiyong CC: "gdb@sourceware.org" Subject: Re: Integrate BLCR to GDB References: <22891922.post@talk.nabble.com> In-Reply-To: <22891922.post@talk.nabble.com> Content-Type: text/plain; charset=us-ascii; format=flowed 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: 2009-04/txt/msg00075.txt.bz2 Zhiyong wrote: > Hi, > If my understanding is correct, current gdb checkpoint/restart is using > fork() and does not support multi-threading. > > I am interested to know if someone has done some work to integrate BLCR > (Berkely Lab Checkpoint/Restart , > https://ftg.lbl.gov/CheckpointRestart/CheckpointRestart.shtml) into gdb? > > As a standalone, BLCR is quite helpful in certain debugging scenarios. But > it is a bit hard to use with gdb , i.e. breakpoints can not be saved and > restart is not convienent to stop at certain point etc. > > BLCR's limitation is it is only for Linux x86 and x86_64. It also needs to > load kernel modules which may or may not be an issue. It is not targeting > debugging but rather process management/fault tolerance. Sounds like a very interesting project. Would you be interested in spearheading it?