Next: BASH Debugger Bugs, Previous: Running, Up: Top [Contents][Index]
You can abbreviate the long name of the BASH debugger command to the first
few letters of the command name, if that abbreviation is unambiguous;
and you can repeat the next or step commands by typing
just RET. Some commands which require a parameter, such as
print remember the argument that was given to them.
| • Command Syntax: | How to give commands to the BASH debugger | |
| • Help: | How to ask for help (help) | |
| • Quit: | Leaving the debugger (quit, kill) | |
| • Stopping: | Stopping and continuing (break, watch, step, cont...) | |
| • Stack: | Examining the stack frame (where, up, down, frame) | |
| • List: | Printing source files (list) | |
| • Edit: | Editing source files (edit) | |
| • Search: | Searching source files (/pat/ ?pat?) | |
| • Data: | Examining data (print, examine, info variables) | |
| • Auto Display: | Executing expressions on stop (display, undisplay) | |
| • Evaluation/Execution: | Arbitrary execution (eval, eval? shell) | |
| • Interfacing to the OS: | Interfacing to the OS (cd, pwd) | |
| • Information and Settings: | Status and Debugger settings (info, show) | |
| • Controlling bashdb: | Controlling bashdb (annotate, file, prompt, history...) |
Next: BASH Debugger Bugs, Previous: Running, Up: Top [Contents][Index]