Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@vmware.com>
To: Sandeep222 <sandeep.srikumar@honeywell.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: store the contents of target’s RAM in frequent intervals
Date: Fri, 05 Dec 2008 19:02:00 -0000	[thread overview]
Message-ID: <493979E2.90707@vmware.com> (raw)
In-Reply-To: <20849726.post@talk.nabble.com>

Sandeep222 wrote:
> Hi,
>             I would like to know if there is any possibility for adding
> functionality in GDB which could store the contents of target’s RAM in
> frequent intervals into hard disk so that, when accidentally switched off or
> shut down of an embedded target, we can resume the execution of the program
> from where it earlier stopped (i.e previous save point). Conceptually It is
> some what similar to the Hibernate function used in Windows xp, Service pack
> 2. I was thinking of inducing this functionality for embedded targets in
> particular. 
>            Need araises when a test program is made to run for days and
> probably weeks. Suppose, if someone switches off the unit on say 2nd day, it
> should be able to continue from that point. Else, the program is made to run
> all over again resulting in wastage of time.

Sounds a lot like a checkpoint.  ;-)

GDB has checkpoint functionality for some native operating systems
(eg. Linux), but not at present for remote (embedded) targets.

It would be cool, but potentially expensive, eg. if it involved
downloading the entire contents of target memory.

Some investment in developing a smart debug agent that ran on the
target side might result in the ability to save, eg., just the parts
of memory that have changed since the last checkpoint.

I've also thought about this in terms of generating a target
core file -- which would also involve sucking a bunch of target
memory over to the host, but in this context, we could use
section start/end addresses at least for some of it, and then
we would need to account for stack and heap...


  reply	other threads:[~2008-12-05 19:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-05  8:39 Sandeep222
2008-12-05 19:02 ` Michael Snyder [this message]
2008-12-06 10:20   ` Nicholas Mc Guire

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=493979E2.90707@vmware.com \
    --to=msnyder@vmware.com \
    --cc=gdb@sourceware.org \
    --cc=sandeep.srikumar@honeywell.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