Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tomas Holmberg <th@virtutech.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: Thiago Jung Bauermann <bauerman@br.ibm.com>,
	  "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFA] Resubmit reverse debugging [5/5]
Date: Mon, 15 Dec 2008 12:29:00 -0000	[thread overview]
Message-ID: <49464D65.9030505@virtutech.com> (raw)
In-Reply-To: <48ED16FE.8010105@vmware.com>

>> What about adding "previous" and either "pr" or "pre" as alias to
>> reverse-next? Sounds more natural to me than "reverse-next". Similarly,
>> "previousi" and "pri" or "prei".
>>
>> I'd also half-seriously suggest adding a "step-back" alias on the same
>> grounds. :-)
> 
> Lots of people have alternate suggestions for command names.
> The present set is as close to convergence as we were able to
> get in several previous rounds of discussion.
> 
> I don't want the feature to be held up by this discussion,
> so I'm just saying "aliases are easy to add later".

I would like to continue the discussion about alias name for the too
long reverse commands. I am not sure that the gdb-patches list is the
right place for having this discussion.

My new command alias suggestions are in the right column:
reverse-continue - reverse
reverse-finish   - uncall
reverse-next     - previous, prev
reverse-nexti    - previousi, previ
reverse-step     - unstep
reverse-stepi    - unstepi

The main reasons for the new alias names is to better describe what
the commands actually do and distinguish them from the "forward"
debugging commands. The reverse- commands implies that running a
program in reverse is only a special mode of running it forward. This
is no longer true and the support for running in reverse will increase
in the future.

/Tomas Holmberg


  parent reply	other threads:[~2008-12-15 12:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-08  2:23 Michael Snyder
2008-10-08 18:15 ` Thiago Jung Bauermann
2008-10-08 19:16   ` Eli Zaretskii
2008-10-09  4:23     ` Pedro Alves
2008-10-09  8:41       ` Eli Zaretskii
2008-10-08 20:14   ` Thiago Jung Bauermann
2008-10-08 20:55     ` Michael Snyder
2008-10-08 20:27   ` Michael Snyder
2008-10-08 20:43     ` Thiago Jung Bauermann
2008-12-15 12:29     ` Tomas Holmberg [this message]
2008-10-08 21:06   ` Michael Snyder
2008-10-08 21:14     ` Thiago Jung Bauermann
2008-10-17 19:48 ` Michael Snyder

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=49464D65.9030505@virtutech.com \
    --to=th@virtutech.com \
    --cc=bauerman@br.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --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