The 'keyboard' command is great for debugging, but if you have multiple instances of keyboard, it is very difficult to tell which one is being called. This complicates debugging somewhat.
kdb() is a drop-in replacement for keyboard, and it shows a stack trace, preview of the next line to be executed, and a hyperlink to that line of code. For example, if foo() calls bar() calls baz() and we have a 'keyboard' command in baz(), the user sees
whereas with kdb() the user sees
baz:2 << bar:2 << foo:3
3 y = x+2;
The '3' is a hyperlink to line 3 of baz.m, and depending on settings the Matlab editor may automatically open to the appropriate kdb() statement. The only caveat is that unlike keyboard, kdb() cannot be the last statement in the function.
Romesh (2020). Keyboard replacement with stack trace (https://www.mathworks.com/matlabcentral/fileexchange/40415-keyboard-replacement-with-stack-trace), MATLAB Central File Exchange. Retrieved .
Thanks for the suggestion, I am also a big fan of eliminating calls to eval() wherever possible. I've submitted an updated version incorporating both your changes
Your idea is very good. I've never been comfortable with KEYBOARD. To me your function provides a "persistent" break-point. However, I have modified the code to handle functions in packages.
stk = dbstack('-completenames');
dbstop( 'in', stk(2).file, 'at', num2str( stk(2).line+1 ) )
Find the treasures in MATLAB Central and discover how the community can help you!Start Hunting!