mdb1
Mercury debugger
Usage
mdb [<options>]
<executable>
[<args>] ...
Overview
`mdb' invokes the specified command `<executable> <args>...' with Mercury debugging enabled. If that command is a Mercury program that was compiled with debugging enabled (e.g. using the `--debug' option), or if that command invokes such a program, then mdb will cause the program to be executed under the supervision of the Mercury internal debugger. Otherwise, mdb will execute the command line as if the mdb prefix weren't there.
By default, all the output of the debugger and the output of the program being debugged will be interleaved on the same terminal window. This can be avoided using the `--tty' or `--window' options described below.
Notes
mdb is one of the development tools that are part of the Mercury distribution.
This manual page is limited to a brief summary. For further information see the Mercury User's Guide.
Options
-t <file-name>, --tty <file-name>
Redirect all of the I/O for the debugger to the device specified by <file-name>. The I/O for the program being debugged will not be redirected.
-w, --window
Run the program in a new window, with the program's I/O going to that window, but with mdb's I/O going to the current terminal.
-c <window-command>, --window-command <window-command>
Specify the command used by the `--window' option for executing a command in a new window. The default such command is `xterm -e'.
Environment
MERCURY_OPTIONS, MERCURY_DEBUGGER_INIT.
Releases
2 releases since Debian 2.2 (Potato); the text changed 1 time.