From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25215 invoked by alias); 9 Dec 2005 21:58:03 -0000 Received: (qmail 25199 invoked by uid 22791); 9 Dec 2005 21:58:02 -0000 X-Spam-Check-By: sourceware.org Received: from bijisan.lojik.net (HELO bijisan.lojik.net) (63.251.19.34) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 09 Dec 2005 21:58:01 +0000 Received: from [127.0.0.1] (bijisan.lojik.net [63.251.19.34]) by bijisan.lojik.net (8.12.6/8.12.6) with ESMTP id jB9LvvTp079359 for ; Fri, 9 Dec 2005 16:57:58 -0500 (EST) (envelope-from greg@bronevetsky.com) Message-ID: <4399FDE5.2020905@bronevetsky.com> Date: Fri, 09 Dec 2005 21:58:00 -0000 From: Greg Bronevetsky User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) MIME-Version: 1.0 To: gdb@sources.redhat.com Subject: Checkpoint-restart with different code Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2005-12/txt/msg00108.txt.bz2 I see that there's been some discussion on this list on checkpointing techniques that may be included in gdb. My research group at Cornell is working on a number of such checkpointers for both sequential and parallel programs and we recently decided to try a more challenging variant of checkpointing where the user can take a checkpoint of their program, modify their source code a bit (add remove stack variables, move function calls around a bit and a few other things) and then resume computation using the modified code. This seems to be very useful for debugging long-running applications since the user would be able to work around the bug without losing a week's or month's worth of results. (can happen in high-performance computing) Similarly, its useful for situations where your execution is in some particularly buggy corner case and you want to keep making modifications and trying them out without having to guide the program's execution back into that corner case after every code change. My question is, has anybody heard of anything that can do this? Obviously, this kind of checkpointing would require compiler support, so gdb wouldn't have done this, but have you heard of any systems/research that has addressed this question? Thanks. -- Greg Bronevetsky 490 Rhodes Hall Cornell University