PR# 12829 Multiple problems with command line debugger

There are multiple problems with the command line debugger.  Here are the ones
I noticed:

1. Output is hard to read because it is run together.  It would be helpful if
   every (or most) debugger menu was preceded by a blank line.

2. Type "a" to set arguments.  Type "a b c" to set 3 arguments.
   Type "i" to display parameters.  Shows just "a" as argument.
   Type "a" again to try to set the arguments.  Don't get any argument prompt.
   Type "a" again.  Type "i".  Now arguments is shown as just "c".
   This is incredibly confusing and not very useful if one cannot set multiple
   arguments.

3. Type "e" to set environment.  Just displays main menu again, without giving
   me a chance to set any environment variables.

4. Type "s" to step into routine, then "d" to display information.
   Get debugger Display menu.  Menu items for locals, arguments, callstack
   and status should all be capitalized (first letter) but are not.
   Also, "list breakpoints" in Breakpoints menu should capitalize "List".

5. Type "e" to evaluate an expression.  Type "hamster" for the expression.
   Correctly reports VEEN, but debugger Display menu heading is on same
   line as VEEN (should be one or two newlines after error so that things
   are readable).

6. Go to debugger Breakpoints menu.  Type "a" to add a breakpoint.
   Type "*" for class name.  Correctly reports that class was not found.
   Type "a" again.  Type "string_8".  Says "could not find class {*}".
   Huh?  I typed "string_8" the second time.  Now try again, but type
   STRING_8.  Now it finds the class (case problem).  Type "*" for all
   features.  Accepts it but listing breakpoints shows no breakpoints.

7. Add breakpoint.  Type STRING_8 for class, "item" for feature and type
   break index 200.  Accepts 200, which can't be valid.  Then says
   "Added breakpoint {TEST}.make@3", which was the previous breakpoint
   I added successfully.  Something is very confused here.

8. Type "m" to modify an existing breakpoint.  Type 400 for the index.
   Now debugger is hung.

I guess that is enough for now.  The command line debugger may be experimental
but it also appears to be almost completely untested.

Those issues should be fixed by revision rev#68663.

Not all the debugger's functionalities are available in TTY debugger, but we are slowly adding them. The main missing feature is the "Interrupt" since for now Ctrl+C is closing the application (debugger) (at least on Windows).