From: "Jakob Engblom" <jakob@virtutech.com>
To: "'lehe'" <timlee126@yahoo.com>, <gdb@sourceware.org>
Subject: RE: Edit-and-Continue and running-backward
Date: Sat, 28 Feb 2009 08:15:00 -0000 [thread overview]
Message-ID: <005701c9997c$ac7c9510$0575bf30$@com> (raw)
In-Reply-To: <22258432.post@talk.nabble.com>
> 2. How to get the ability to run programs backward? What is "target
> environment" in this description "If the target environment supports it, gdb
> can allow you to “rewind” the program by running it backward" and how to
> make my target environment support it? I am programming sometimes in Linux
> with emacs or with IDE Code::Blocks.
There is some kind of work on "record and replay" for user-land Linux processes that Teawater is working on.
You can also use hte commercial VmWare and Simics tools to get full-system reverse execution, which are available today. Both work with any gdb-remote-based system.
Note that edit-and-continue cannot reasonably be combined with reverse execution: what would it mean to back through an execution trace where you change the code underlying it? You could reasonably back up to some previous point in time, do the patch, and then execute into it. However, you probably will have to consider the point in time of the patch the staring point of your reversible session -- unless the execution substrate can remember and redo and undo the patch as you execute over the patch point in time.
Best regards,
/jakob
_______________________________________________________
Jakob Engblom, PhD, Technical Marketing Manager
Virtutech Direct: +46 8 690 07 47
Drottningholmsvägen 22 Mobile: +46 709 242 646
11243 Stockholm Web: www.virtutech.com
Sweden
________________________________________________________
prev parent reply other threads:[~2009-02-28 8:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-28 3:27 lehe
2009-02-28 6:16 ` Joel Brobecker
2009-02-28 8:15 ` Jakob Engblom [this message]
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='005701c9997c$ac7c9510$0575bf30$@com' \
--to=jakob@virtutech.com \
--cc=gdb@sourceware.org \
--cc=timlee126@yahoo.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