From: Greg Bronevetsky <greg@bronevetsky.com>
To: gdb@sources.redhat.com
Subject: Checkpoint-restart with different code
Date: Fri, 09 Dec 2005 21:58:00 -0000 [thread overview]
Message-ID: <4399FDE5.2020905@bronevetsky.com> (raw)
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
next reply other threads:[~2005-12-09 21:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-09 21:58 Greg Bronevetsky [this message]
2005-12-09 22:08 ` Daniel Jacobowitz
2005-12-10 1:36 ` Randolph Chung
2005-12-10 20:34 ` Greg Bronevetsky
2005-12-11 3:53 ` Daniel Jacobowitz
2005-12-13 19:58 Prateek Saxena
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4399FDE5.2020905@bronevetsky.com \
--to=greg@bronevetsky.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox