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

[Dave Anderson]

----- Original Message -----
> On 03/14/12 06:37, Dave Anderson wrote:
> 
> Well, ok, I kept stumble fingering the gdb commands, so here's a working patch.
> Under the covers, the "cmd_gdb" peeks into the command when it sees it is a
> "set" command.  It already does this.  But if it is a "set gdb" command, then
> it just redirects to the internal "cmd_set" function.  I also jiggered the
> arguments to accommodate the fact that the first argument is no longer "gdb".
> And I fixed the prompt to be "gdb> " to distinguish from both "crash> " and
> "(gdb) ".  I also really hate procedures that go beyond 100 lines or so,
> so I did not add to the cmd_set length.

Hi Bruce,

I just ran a quick test of your patch, and one thing I noted 
immediately is when running "set variable" with no argument,
which should just show the current setting:

  crash> help set
  ...
    This command may also be used to set internal crash variables.  If no value
    argument is entered, the current value of the crash variable is shown.  These
    are the crash variables, acceptable arguments, and purpose:
  ...

But with your patch, 
  
  crash> set scroll
  scroll: on (/usr/bin/less)
  crash> set debug
  debug: 0
  crash> set silent
  silent: off
  crash> set gdb
  Segmentation fault
  $

I'm not exactly sure why it works OK for the other variables, 
but not for "gdb".  Anyway, I'll get back to it on Monday...

Thanks,
  Dave