From: "Jakob Engblom" <jakob@virtutech.com>
To: "'Eli Zaretskii'" <eliz@gnu.org>
Cc: <gdb-patches@sourceware.org>
Subject: RE: GDB MI Reverse Commands added [2 of 3]
Date: Fri, 28 Aug 2009 10:08:00 -0000 [thread overview]
Message-ID: <002b01ca27c7$1316d8c0$39448a40$@com> (raw)
In-Reply-To: <83tyzucw8p.fsf@gnu.org>
> > ! 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?
What about this?
"Resumes the execution of the inferior program until a breakpoint is
encountered, or until the inferior exits. If the @samp{--reverse}
option is specified, resumes the reverse execution of the inferior
program until a breakpoint is encountered, or until the execution
reaches that start of the inferior. "
Here, I generalize the "inferior" so that if debugging on naked hardware, exit
really means the target rebooting or something like that.
> > ! Mode}), if the @samp{--all} is not specified, only the thread
> > ! specified with the @samp{--thread} option (or current thread, if no
> > ! @samp{--thread} is provided) is resumed. If @samp{--all} is
>
> What `--thread' option are you talking about here? There was no such
> option in the "Synopsis" part above.
And I cannot see that the code parses it either... so it will be fixed. I
apologize, but I am put as the messenger for a team effort...
/jakob
next prev parent reply other threads:[~2009-08-28 10:05 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
2009-08-28 10:05 ` Eli Zaretskii
2009-08-28 10:08 ` Jakob Engblom [this message]
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='002b01ca27c7$1316d8c0$39448a40$@com' \
--to=jakob@virtutech.com \
--cc=eliz@gnu.org \
--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