From: "Jakob Engblom" <jakob@virtutech.com>
To: <gdb-patches@sourceware.org>
Subject: RE: GDB MI Reverse Commands added [2 of 3]
Date: Thu, 27 Aug 2009 13:48:00 -0000 [thread overview]
Message-ID: <020101ca26f0$202d0bb0$60872310$@com> (raw)
In-Reply-To: <83tyzucw8p.fsf@gnu.org>
> > Resumes the execution of the inferior program until a breakpoint is
> > ! encountered, or until the inferior exits. If the @samp{--reverse}
> ^^
> Two spaces between sentences, please (here and elsewhere).
Will do.
> > ! option is specified, resumes the reverse execution of the inferior
> > ! program until a breakpoint is encountered, or until the inferior
> > ! exits.
>
> How can you exit in reverse? I think you can only get to the
> beginning of `main', no?
It really depends on how your backend works... there is no necessary
relationship between some function called "main" and where revexec starts.
First of all, in a full-system reverse debug case, it is quite reasonable to
"exit backwards" and get to the point BEFORE the program started. Just like you
can get to AFTER exit if you let the program run its course.
It gets even funkier if you let the backend be OS aware. In this case, the
target program is only being debugged when actually execution on some
targetsystem processor. At other times, there is no execution activity, as the
program is not running. Here also, you can easily see how a mistaken reverse
just goes back to before the program even existed, essentially a limbo analogous
to after exit.
There is also normally a point in time where reverse starts being available.
That could be when the user turns it on DURING the execution of program, or the
first instruction of a booting machine, or some other event horizon before which
we have no information. On a hardware trace box, it just the start of the
sliding window of visibility.
So I think this makes sense, no?
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
________________________________________________________
next prev parent reply other threads:[~2009-08-27 8:26 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-26 14:38 Jakob Engblom
2009-08-26 17:38 ` Eli Zaretskii
2009-08-27 13:48 ` Jakob Engblom [this message]
2009-08-28 10:05 ` Eli Zaretskii
2009-08-28 10:08 ` Jakob Engblom
2009-08-28 10:49 ` Eli Zaretskii
2009-08-28 13:41 ` Greg Law
2009-08-28 14:28 ` Eli Zaretskii
2009-08-28 17:12 ` Greg Law
2009-08-28 17:34 ` Eli Zaretskii
2009-08-28 18:49 ` Michael Snyder
2009-08-28 21:32 ` Eli Zaretskii
2009-08-28 23:28 ` Michael Snyder
2009-08-29 8:12 ` Eli Zaretskii
2009-08-29 15:19 ` Eli Zaretskii
2009-08-31 12:14 ` Jakob Engblom
2009-08-31 13:06 ` Jakob Engblom
2009-08-31 15:46 ` Hui Zhu
2009-08-31 16:47 ` Eli Zaretskii
2009-09-01 6:41 ` Jakob Engblom
2009-12-15 19:41 ` Michael Snyder
2009-12-16 8:01 ` Vladimir Prus
2009-12-16 18:10 ` Eli Zaretskii
2009-12-16 18:15 ` Eli Zaretskii
2009-12-16 19:04 ` Michael Snyder
2009-12-16 20:01 ` Eli Zaretskii
2009-12-16 20:45 ` Vladimir Prus
2009-12-17 20:15 ` Eli Zaretskii
2010-02-12 21:36 ` Michael Snyder
2009-08-31 17:56 ` Michael Snyder
2009-09-01 6:37 ` Jakob Engblom
2009-08-29 7:37 ` Jakob Engblom
2009-08-28 10:44 ` Jakob Engblom
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='020101ca26f0$202d0bb0$60872310$@com' \
--to=jakob@virtutech.com \
--cc=gdb-patches@sourceware.org \
/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