We hope you find the
gawk debugger useful and enjoyable to work with,
but as with any program, especially in its early releases, it still has
some limitations. A few which are worth being aware of are:
gawkinternals), you will realize that much of the internal manipulation of data in
gawk, as in many interpreters, is done on a stack.
Op_pop, etc., are the “bread and butter” of most
gawkcode. Unfortunately, as of now, the
gawkdebugger does not allow you to examine the stack’s contents.
That is, the intermediate results of expression evaluation are on the stack, but cannot be printed. Rather, only variables which are defined in the program can be printed. Of course, a workaround for this is to use more explicit variables at the debugging stage and then change back to obscure, perhaps more optimal code later.
awkprogrammer, you are expected to know what
gawkdebugger is designed to be used by running a program (with all its parameters) on the command line, as described in Debugger Invocation. There is no way (as of now) to attach or “break in” to a running program. This seems reasonable for a language which is used mainly for quickly executing, short programs.
gawkdebugger only accepts source supplied with the -f option.
Look forward to a future release when these and other missing features may be added, and of course feel free to try to add them yourself!