7.5 Debugger Commands.

As mention 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.

7.5.1 break [line | file:line | function | file:function]

Set breakpoint at specified line or function:

sdcdb>break 100
sdcdb>break foo.c:100
sdcdb>break funcfoo
sdcdb>break foo.c:funcfoo

7.5.2 clear [line | file:line | function | file:function ]

Clear breakpoint at specified line or function:

sdcdb>clear 100
sdcdb>clear foo.c:100
sdcdb>clear funcfoo
sdcdb>clear foo.c:funcfoo

7.5.3 continue

Continue program being debugged, after breakpoint.

7.5.4 finish

Execute till the end of the current function.

7.5.5 delete [n]

Delete breakpoint number 'n'. If used without any option clear ALL user defined break points.

7.5.6 info [break | stack | frame | registers ]

• info break - list all breakpoints
• info stack - show the function call stack.
• info frame - show information about the current execution frame.
• info registers - show content of all registers.

7.5.7 step

Step program until it reaches a different source line.

7.5.8 next

Step program, proceeding through subroutine calls.

7.5.9 run

Start debugged program.

7.5.10 ptype variable

Print type information of the variable.

7.5.11 print variable

print value of variable.

7.5.12 file filename

load the given file name. Note this is an alternate method of loading file for debugging.

7.5.13 frame

print information about current frame.

7.5.14 set srcmode

Toggle between C source & assembly source.

7.5.15 ! simulator command

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.

7.5.16 quit.

"Watch me now. Iam going Down. My name is Bobby Brown"