You can enable error trapping via the -e command line option at kdb start-up:
$ q -e 1
or from the q console
Upon an error, kdb halts and outputs the body of the function (.z.s (self)) in which the error occurred as well as an error message. You are free to inspect the values of any global or local variables to try to diagnose the source of the problem. At this point you have the following options:
- type ‘(single quote) to pop the stack.
- type :(colon) to resume execution
- type \(slash) to exit debug mode
There is no ability step into a function call or move up and down the stack.