|
NAMEsdb - SNOBOL4 debuggerSYNOPSISsdb [ options ... ] program.snoDESCRIPTIONsdb is a debugger for snobol4(1) programs, in the mold (clawning fone) of gdb(1), The GNU debugger. sdb(1) uses readline(3) for command line editing/history when available.Commands
A blank line repeats the previous command. Non-ambiguous abbreviations of commands can be used (ie; s, n). The GNU Readline library (when available) will be used for sdb(1) input for command editing and history. The keyboard interrupt character (eg; Control-C) will stop a running program and return control to the sdb(1) command prompt. If your program calls the SDB() function, it will act as a
breakpoint. You can check whether sdb(1) is loaded with the
FUNCTION() predicate, ie;
FUNCTION('SDB') SDB() FILES
SEE ALSOsnobol4(1), gdb(1), readline(3), snobol4readline(3)AUTHORPhilip L. BudneInspired by Fred Weigel's DDT.SNO and SITBOL's SNODDT. LIMITATIONSsdb(1) uses a wide variety of system facilities and will interact poorly with any programs that use any number of features, including:
BUGSIf you try to put a breakpoint on a label or line with no code or goto fields, the breakpoint will never be triggered.You cannot put a breakpoint on the END label (however control always returns to sdb when the END label is reached). Interrupt character trapping is in it's infancy, and only occurs at the start of a each statement executed. The interrupt character is silently ignored when at the sdb command prompt. Leaves an unprotected listing file of the sources in the /tmp directory (create a protected directory?). ``quit'' and ``run'' commands say program is running even if first line of the program has not yet been executed! Some fatal errors cannot be trapped, and sdb will be terminated.
Visit the GSP FreeBSD Man Page Interface. |