Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Michael Snyder <msnyder@vmware.com>
Cc: glaw@undo-software.com, jakob@virtutech.com, gdb-patches@sourceware.org
Subject: Re: GDB MI Reverse Commands added [2 of 3]
Date: Sat, 29 Aug 2009 08:12:00 -0000	[thread overview]
Message-ID: <838wh3awdy.fsf@gnu.org> (raw)
In-Reply-To: <4A9865A5.1020703@vmware.com>

> Date: Fri, 28 Aug 2009 16:17:57 -0700
> From: Michael Snyder <msnyder@vmware.com>
> CC: "glaw@undo-software.com" <glaw@undo-software.com>, 
>  "jakob@virtutech.com" <jakob@virtutech.com>,
>  "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
> 
> How about this?  (please add markups)
> 
> Resumes the execution of the inferior program, which will continue
> to execute until it reaches a debugger stop event.  If the 
> @samp{--reverse} option is specified, execution resumes in reverse until 
> it reaches a stop event.  Stop events may include
>   * breakpoints or watchpoints
>   * signals or exceptions)
>   * the end of the process (or its beginning if --reverse)
>   * the end (beginning) of a replay log if one is being used.

Fine with me (except for a couple of tiny changes).

    Resumes the execution of the inferior program, which will continue
    to execute until it reaches a debugger stop event.  If the 
    @samp{--reverse} option is specified, execution resumes in reverse until 
    it reaches a stop event.  Stop events may include
    @itemize @bullet
    @item
    breakpoints or watchpoints
    @item
    signals or exceptions
    @item
    the end of the process (or its beginning under @samp{--reverse})
    @item
    the end or beginning of a replay log if one is being used.
    @end @itemize


  reply	other threads:[~2009-08-29  7:53 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
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 [this message]
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=838wh3awdy.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=glaw@undo-software.com \
    --cc=jakob@virtutech.com \
    --cc=msnyder@vmware.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