Next: Help commands, Previous: I/O tabling commands, Up: Debugger commands [Contents][Index]
mmc_options option1 option2 …This command sets the options that will be passed to ‘mmc’ to compile your query when you use one of the query commands: ‘query’, ‘cc_query’, or ‘io_query’. For example, if a query results in a compile error, it may sometimes be helpful to use ‘mmc_options --verbose-error-messages’.
printlevel noneSets the default print level to ‘none’.
printlevel someSets the default print level to ‘some’.
printlevel allSets the default print level to ‘all’.
printlevelReports the current default print level.
scroll onTurns on user control over the scrolling of sequences of event reports. This means that every screenful of event reports will be followed by a ‘--more--’ prompt. You may type an empty line, which allows the debugger to continue to print the next screenful of event reports. By typing a line that starts with ‘a’, ‘s’ or ‘n’, you can override the print level of the current command, setting it to ‘all’, ‘some’ or ‘none’ respectively. By typing a line that starts with ‘q’, you can abort the current debugger command and get back control at the next event.
scroll offTurns off user control over the scrolling of sequences of event reports.
scroll sizeSets the scroll window size to size,
which tells scroll control to stop and print a ‘--more--’ prompt
after every size - 1 events.
The default value of size
is the value of the LINES environment variable,
which should correspond to the number of lines available on the terminal.
scrollReports whether user scroll control is enabled and what the window size is.
stack_default_limit sizeSet the default number of lines printed by the ‘stack’ and ‘nondet_stack’ commands to size. If size is zero, the limit is disabled.
goal_paths onTurns on printing of goal paths at events.
goal_paths offTurns off printing of goal paths at events.
goal_pathsReports whether goal paths are printed at events.
scope allSets the default scope of new breakpoints to “all”, i.e. by default, new breakpoints on procedures will stop at all events in the procedure.
scope interfaceSets the default scope of new breakpoints to “interface”, i.e. by default, new breakpoints on procedures will stop at all interface events in the procedure.
scope entrySets the default scope of new breakpoints to “entry”, i.e. by default, new breakpoints on procedures will stop only at events representing calls to the procedure.
scopeReports the current default scope of new breakpoints.
echo onTurns on the echoing of commands.
echo offTurns off the echoing of commands.
echoReports whether commands are being echoed or not.
context noneWhen reporting events or ancestor levels, does not print contexts (filename/line number pairs).
context beforeWhen reporting events or ancestor levels, prints contexts (filename/line number pairs) before the identification of the event or call to which they refer, on the same line. With long fully qualified predicate and function names, this may make the line wrap around.
context afterWhen reporting events or ancestor levels, prints contexts (filename/line number pairs) after the identification of the event or call to which they refer, on the same line. With long fully qualified predicate and function names, this may make the line wrap around.
context prevlineWhen reporting events or ancestor levels, prints contexts (filename/line number pairs) on a separate line before the identification of the event or call to which they refer.
context nextlineWhen reporting events or ancestor levels, prints contexts (filename/line number pairs) on a separate line after the identification of the event or call to which they refer.
contextReports where contexts are being printed.
user_event_context noneWhen reporting user-defined events, does not print either filename/line number pairs or procedure ids.
user_event_context fileWhen reporting user-defined events, prints only filename/line number pairs, not procedure ids.
user_event_context procWhen reporting user-defined events, prints only procedure ids, not filename/line number pairs.
user_event_context fullWhen reporting user-defined events, prints both filename/line number pairs and procedure ids.
user_event_contextReports what parts of the context are being printed at user events.
list_context_lines numSets the number of lines to be printed by the ‘list’ command printed before and after the target context.
list_context_linesPrints the number of lines to be printed by the ‘list’ command printed before and after the target context.
list_path dir1 dir2 …The ‘list’ command searches a list of directories when looking for a source code file. The ‘list_path’ command sets the search path to the given list of directories.
list_pathWhen invoked without arguments, the ‘list_path’ command prints the search path consulted by the ‘list’ command.
push_list_dir dir1 dir2 …Pushes the given directories on to the search path consulted by the ‘list’ command.
pop_list_dirPops the leftmost (most recently pushed) directory from the search path consulted by the ‘list’ command.
list_cmd ExternalCommandTells mdb that all future ‘list’ commands should be handled by ExternalCommand. The command will be called with four arguments: the source file name, the first line number (counting from 1), the last line number, the current line number. The command should print all the lines from the first to the last, both inclusive, with the current line marked (or highlighted) in some fashion to standard output, and report any errors to standard error.
If ExternalCommand is ‘none’ then the ‘list’ command will revert to printing source listings internally.
list_cmdWhen invoked without arguments, the ‘list_cmd’ command prints the last value set by the ‘list_cmd’ command.
fail_trace_counts filenameThe declarative debugger can exploit information about the failing and passing test cases to ask better questions. This command tells the ‘dice’ command that filename contains execution trace counts from failing test cases. The ‘dice’ command will use this file unless this is overridden with its ‘--fail-trace-counts’ option.
fail_trace_countsPrints the name of the file containing execution trace counts from failing test cases, if this has already been set.
pass_trace_counts filenameThe declarative debugger can exploit information about the failing and passing test cases to ask better questions. This command tells the ‘dice’ command that filename contains execution trace counts from passing test cases. The ‘dice’ command will use this file unless this is overridden with its ‘--pass-trace-counts’ option.
pass_trace_countsPrints the name of the file containing execution trace counts from passing test cases, if this has already been set.
max_io_actions numSet the maximum number of I/O actions to print in questions from the declarative debugger to num.
max_io_actionsPrints the maximum number of I/O actions to print in questions from the declarative debugger.
web_browser_cmd commandSet the shell command used to launch a web browser to command.
web_browser_cmdPrints the shell command used to launch a web browser, if this has been set.
format [-APB] formatSets the default format of the browser to format, which should be one of ‘flat’, ‘pretty’ or ‘verbose’.
The browser maintains separate configuration parameters for the three commands ‘print *’, ‘print var’, and ‘browse var’. A ‘format’ command applies to all three, unless it specifies one or more of the options ‘-A’ or ‘--print-all’, ‘-P’ or ‘--print’, and ‘-B’ or ‘--browse’, in which case it will set only the selected command’s default format.
format_param [-APBfpv] param valueSets one of the parameters of the browser to the given value. The parameter param must be one of ‘depth’, ‘size’, ‘width’ and ‘lines’.
The browser maintains separate configuration parameters for the three commands ‘print *’, ‘print var’, and ‘browse var’. A ‘format_param’ command applies to all three, unless it specifies one or more of the options ‘-A’ or ‘--print-all’, ‘-P’ or ‘--print’, and ‘-B’ or ‘--browse’, in which case it will set only the selected command’s parameters.
The browser also maintains separate configuration parameters for the different output formats: flat, pretty and verbose. A ‘format_param’ command applies to all of these, unless it specifies one or more of the options ‘-f’ or ‘--flat’, ‘-p’ or ‘--pretty’, and ‘-v’ or ‘--verbose’, in which case it will set only the selected format’s parameter.
alias name command [command-parameter …]Introduces name as an alias for the given command with the given parameters. Whenever a command line has name as its first word, the debugger will substitute the given command and parameters for this word before executing the command line.
If name is the upper-case word ‘EMPTY’, the debugger will substitute the given command and parameters whenever the user types in an empty command line.
If name is the upper-case word ‘NUMBER’, the debugger will insert the given command and parameters before the command line whenever the user types in a command line that consists of a single number.
unalias nameRemoves any existing alias for name.
Next: Help commands, Previous: I/O tabling commands, Up: Debugger commands [Contents][Index]