Hi
does anyone know what the commands are for the mvBase Debugger
Thanks, Rowland

From memory, the key ones are :

E[n] - no of lines to execute before hitting the debugger again (ie E1 will
set the debugger to line by line execution. E on it's own sets for
unlimited lines
G - Continue execution for no of lines set by E command.
/var - displays the contents of variable var
/var=xxx - sets variable var to xxx
B$=999 - sets a a breakpoint at line no (999 in this case)

I think thats enough to get you going!

Anything else thats needed?

Regards
Simon
"Rowland Long" <rhl (AT) jwba (DOT) com> wrote

Simon Verona once wrote in <42f29acd$0$91511$ed2e19e4@ptn-nntp-
reader04.plus.net>...
Once you're at the debug prompt, do E1 to set single step.

CTRL-J will then execute a line at a time instead of G (the two are
probably interchangeable). E0 goes back to regular execution.

S1-20 displays source lines 1 through 20. If the debugger hasn't been
able to find the source, you can override that with the Z command, i.e.

Z filename item

If you're brave, /* dumps all used variables. Beware any that contain
screen positioning codes!

You can also break on a variable value. '$' (as mentioned by Simon) is a
special case for line number. If you wanted to stop when I=42, it's

BI=42

From memory, 'Kx' kills breakpoint 'x'.

There's also a trace feature which may just be T<variable> to
automatically dump <variable> at each break point.

'>>>' will, again from memory get you into a TCL shell whilst keeping
the debug process going. '<<' gets you back out. Take these with a pinch
of salt - I use this feature infrequently.

....plus a bit :-)

--
David Morris

Simon Verona wrote:
Some others that I find very useful:

T - as you step through the program, the code will be displayed line by
line (you may need to precede this with Z filename to specify where to
read the code from).

T[var] (where [var] is the variable name) - as you step through the
program, the value of var will be displayed at each step.

L[n] - displays line [n] of the code (again you may need to do Z
filename first). Very handy when you have an unassigned
variable/non-numeric data and you want to see what variables are used at
that line.


G[n] - continues from line [n], particularly useful if you want to get
out of a loop or bypass a program call.

--
Danny Colyer (the UK company has been laughed out of my reply address)
<URL:http://www.speedy5.freeserve.co.uk/danny/>
"He who dares not offend cannot be honest." - Thomas Paine

It's funny trying to do a brain dump of information...

I've worked with the mvBASE debugger for 20 years (back to the days of ADDS
Mentor!) and whilst I know all those commands, they didn't jump to mind when
I wrote my list... Particularly, the <CTRL+J> one instead of G... I
actually never use G in preference to CTRL-J.

Actually, the debugger is one area where I believe that mvBASE is far
superior to jBase (which we now use). I find the jBase debugger very
capable, but very fiddly.

One other item that comes to mind is the Gnnn which will continue execution
at line nnn... So, for example if you are debugging and spot a bug for
example caused by a variable not being set right, you can test it out by
changing the variable and then using G[lineno] to go back up and rerun the
bit of code again... This is one thing I wish that jBase supported!

Regards
Simon
"David Morris" <david (AT) davidm (DOT) demon.co.uk> wrote