As mentioned earlier the command interface for the debugger has been deliberately kept as close the GNU debugger gdb, as possible. This will help the integration with existing graphical user interfaces (like ddd, xxgdb or xemacs) existing for the GNU debugger. If you use a graphical user interface for the debugger you can skip this section.
Set breakpoint at specified line or function:
sdcdb>break 100
sdcdb>break foo.c:100
sdcdb>break funcfoo
sdcdb>break foo.c:funcfoo
Clear breakpoint at specified line or function:
sdcdb>clear 100
sdcdb>clear foo.c:100
sdcdb>clear funcfoo
sdcdb>clear foo.c:funcfoo
Continue program being debugged, after breakpoint.
Execute till the end of the current function.
Delete breakpoint number 'n'. If used without any option clear ALL user defined break points.
Step program until it reaches a different source line. Note: pressing <return> repeats the last command.
Step program, proceeding through subroutine calls.
Start debugged program.
Print type information of the variable.
print value of variable.
load the given file name. Note this is an alternate method of loading file for debugging.
print information about current frame.
Toggle between C source & assembly source.
Send the string following '!' to the simulator, the simulator response is displayed. Note the debugger does not interpret the command being sent to the simulator, so if a command like 'go' is sent the debugger can loose its execution context and may display incorrect values.
"Watch me now. Iam going Down. My name is Bobby Brown"