The addition of the reverse execution commands (reverse-search, ...) has broken the command abbreviation "rev" for reverse-search. On the other hand, the ninth edition of the GDB manual documents rev as the official abbreviation for reverse-search. Please reinstate this behavior! Typing reverse-search just to disambiguate it from the reverse execution commands, which are supported for a tiny number of platforms, is too painful ---yes, I know about autocompletion, but it doesn't/hasn't work/ed for all platforms. Furthermore, the original designers of GDB clearly intended and documented rev to mean reverse-search, and it has for many releases. s always means step, so GDB supports "hard-wired" abbreviations. Thanks, Konrad Schwarz
Sorry, the above example for a reverse-execution command should have been reverse-step.
I just noticed that "fo" for forward-search is also broken.
There is not "add_alias_cmd" for "reverse-search". But can find a line "You can abbreviate this command as @code{rev}." in @kindex reverse-search. Michael, what do you think about this issue?
Subject: Re: rev abbreviation for reverse-search no longer works teawater at gmail dot com wrote: > ------- Additional Comments From teawater at gmail dot com 2009-09-24 02:52 ------- > There is not "add_alias_cmd" for "reverse-search". > > But can find a line "You can abbreviate this command as @code{rev}." in @kindex > reverse-search. > > Michael, what do you think about this issue? I agree -- reverse-search should have precedence, since it was implemented before the others.
Fixed in 7.2.