[Crash-utility] "gdb" by itself ought to put crash into a "gdb" mode

[Bruce Korb]

On Wed, Mar 14, 2012 at 10:37 AM, Dave Anderson <anderson at redhat.com> wrote:
> I would prefer a usage that's either a command and its
> option, such as "gdb on" and "gdb off", or my original
> suggestion of using the "set" command to set your flags2
> mode bit.  (and which would be documented in their
> respective help page).  And I'm not clear on what
> you mean by "reserved command checking", but maybe

I spelled "restricted" as "reserved" :)

	/*
	 *  If the command is not restricted, pass it on.
	 */
	if (!is_restricted_command(av[0], FAULT_ON_ERROR)) {
> using "set gdb on" as a clear epoch would help?

Probably would, so "another day" I'll give that a spin.
And I'll fiddle the command prompt....