Debug Commands and Arguments

[mcollins]

From comparing the various javascript debugging protocols I've noticed
that the commands for the debug operations ("break", "continue",
"setbreakpoint") have very little variance across protocols, for the
most part. However the arguments and parameters for many of the
commands do vary to a greater degree, so one of the things I have been
considering is whether most of these differences could be reconciled.

One curious example I have found so far is in the V8 debugger
protocol, which allows a 'stepcount' parameter to its continue
command. Presumably this allows execution of multiple lines with a
single step command, but I haven't come across an end-user debugger
interface which allows this. I'm also at a loss to construct an
example of a case where this feature would be useful, so I thought I
would put it to this group to see if anyone else could speculate as to
its purpose.

mc

[Patrick Mueller]

On Jul 27, 2009, at 2:28 PM, mcollins wrote:

> One curious example I have found so far is in the V8 debugger
> protocol, which allows a 'stepcount' parameter to its continue
> command. Presumably this allows execution of multiple lines with a
> single step command, but I haven't come across an end-user debugger
> interface which allows this. I'm also at a loss to construct an
> example of a case where this feature would be useful, so I thought I
> would put it to this group to see if anyone else could speculate as to
> its purpose.

gdb has a step count:

http://sourceware.org/gdb/current/onlinedocs/gdb_6.html#SEC43

I can't think of a useful case myself though.

Patrick Mueller - http://muellerware.org/

[Joe Walker]

Some graphical IDEs have a "Run To Line" command, which could use this. Clearly there are other ways to do the same thing though.
Joe.