Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tomas Holmberg <th@virtutech.com>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: reverse for GDB/MI
Date: Fri, 19 Dec 2008 08:26:00 -0000	[thread overview]
Message-ID: <494B5A82.4020004@virtutech.com> (raw)
In-Reply-To: <gid1vj$irm$1@ger.gmane.org>

Vladimir Prus wrote:
> Tomas Holmberg wrote:
> 
>>> I am not quite sure about adding new set of commands for that. Can we use
>>> --reverse option, thereby not introducing new commands?
>> Adding a reverse option to the existing commands is possible. But I do
>> not think it is a good idea. It is not always obvious what should
>> happen when running a standard command in reverse. 
> 
> Why? -exec-step always steps forward. -exec-step --reverse always steps
> backward. Seems like a fairly simple model to me.

There are other reverse commands than the -exec-reverse-step that are more
complicated. If you consider all reverse commands to be simple variants
of the forward commands, then you are correct that there should just
be a --reverse option. But I consider them to not be simple variants.

You can also look at the documentation to see if the reverse commands are
just variants of the forward variants. I do not think we can replace the
documentation for reverse-step, reverse-step-instruction, reverse-continue,
reverse-finish, reverse-next, and reverse-next-instruction and just say it
is the reverse variant for the corresponding forward commands. Please look
at the other reverse commands and see if you can say "reverse-finish" is
just the reverse variant of finish.

/tomas


  parent reply	other threads:[~2008-12-19  8:26 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-15 10:59 Tomas Holmberg
2008-12-15 18:52 ` Marc Khouzam
2008-12-16  8:44   ` Jakob Engblom
2008-12-16 14:45     ` Marc Khouzam
2008-12-15 20:50 ` Eli Zaretskii
2008-12-17 14:57   ` Tomas Holmberg
2008-12-17 16:41     ` Eli Zaretskii
2008-12-17 16:17 ` Vladimir Prus
2008-12-18  8:33   ` Tomas Holmberg
2008-12-18  8:35     ` Vladimir Prus
2008-12-18  9:16       ` Jakob Engblom
2009-02-05  9:38         ` Vladimir Prus
2009-02-06  4:11           ` Doug Evans
2009-02-06 10:08           ` Jakob Engblom
2009-02-06 10:49             ` Vladimir Prus
2009-02-06 13:56               ` Jakob Engblom
2008-12-19  8:26       ` Tomas Holmberg [this message]
2008-12-19 11:07         ` Joel Brobecker
2008-12-19 13:22           ` Pedro Alves
2008-12-19 13:32             ` Jakob Engblom
2008-12-19 19:11         ` Michael Snyder
2008-12-22 20:27           ` Marc Khouzam
2008-12-22 21:14             ` Michael Snyder
2008-12-22 21:16               ` Marc Khouzam
2009-01-03 18:09             ` Jakob Engblom
2009-01-20 18:22               ` Marc Khouzam
2009-01-21  5:23                 ` teawater
2009-01-21 15:21                 ` Tomas Holmberg
2009-02-05 12:08                 ` Vladimir Prus
2008-12-18 21:39     ` Michael Snyder
2008-12-19  9:10       ` Tomas Holmberg

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=494B5A82.4020004@virtutech.com \
    --to=th@virtutech.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=vladimir@codesourcery.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