This is the mail archive of the
mailing list for the GDB project.
RE: Checkpoint-restart with different code
- From: Prateek Saxena <prateeksaxena at gmail dot com>
- To: greg at bronevetsky dot com
- Cc: gdb at sources dot redhat dot com, drow at false dot org
- Date: Tue, 13 Dec 2005 14:58:25 -0500
- Subject: RE: Checkpoint-restart with different code
I have a stable kernel patch for Linux 126.96.36.199 and Linux 2.4.31 that
allows a process to mmap any region of the tracee's process address
space, through the /proc/[pid]/mem file.
It allows the debugger/tracer to write/read change all parts of the
program memory of traced process. You could you this interface to
modify the code memory being read by the traced process, by simply
mmaping the code/stack/data page in the checkpointer's memory, and
writing to it.
I have tested some large tracer's with this, and the fsx testsuite.
The patches should be available for download in the next week or so. I
can send the link as soon as I upload them.
-- Prateek Saxena
Department of Computer Science,
Stony Brook University.
Greg Bronevetsky wrote:
> 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.
>490 Rhodes Hall