diff options
| author | Jose Antonio Ortega Ruiz <jao@gnu.org> | 2001-07-13 20:17:04 +0000 |
|---|---|---|
| committer | Jose Antonio Ortega Ruiz <jao@gnu.org> | 2001-07-13 20:17:04 +0000 |
| commit | b18af386c53f81e31f98a1c1b699666ec69a7aa4 (patch) | |
| tree | 86b5b6e96fa98834b01405ac2183a622ac2af5ae /doc/mdk_gstart.texi | |
| parent | 6b57caa914cf2ad0586eb7a90606cc5d50ca1cb1 (diff) | |
| download | mdk-b18af386c53f81e31f98a1c1b699666ec69a7aa4.tar.gz mdk-b18af386c53f81e31f98a1c1b699666ec69a7aa4.tar.bz2 | |
version 0.4
Diffstat (limited to 'doc/mdk_gstart.texi')
| -rw-r--r-- | doc/mdk_gstart.texi | 17 |
1 files changed, 12 insertions, 5 deletions
diff --git a/doc/mdk_gstart.texi b/doc/mdk_gstart.texi index 1fee48c..4c8b025 100644 --- a/doc/mdk_gstart.texi +++ b/doc/mdk_gstart.texi @@ -170,9 +170,14 @@ its output device (@pxref{Writing a source file}), the output is redirected to the shell's standard output. Had you used any other MIX output devices (disks, drums, line printer, etc.), @code{mixvm} would have created a file named after the device used (e.g. @file{disk4.dev}) -and written its output there. Note also that the virtual machine reports -the execution time of the program, according to the (virtual) time spent -in each of the binary instructions (@pxref{Execution times}). +and written its output there@footnote{The device files are stored, by +default, in a directory called @file{.mdk}, which is created in your +home directory the first time @code{mixvm} is run. You can change this +default directory using the command @code{devdir} when running +@code{mixvm} in interactive mode (@pxref{Configuration commands})}. Note +also that the virtual machine reports the execution time of the program, +according to the (virtual) time spent in each of the binary instructions +(@pxref{Execution times}). Sometimes, you will prefer to store the results of your program in MIX registers rather than writing them to a device. In such cases, @@ -276,7 +281,9 @@ elapsed execution time (i.e., the time spent executing instructions since the last breakpoint), the total execution time for the program up to now (which in our case coincides with the elapsed time, since there were no breakpoints), and the total uptime for the virtual machine (you -can load and run more than one program in the same session). After +can load and run more than one program in the same +session)@footnote{Printing of timing statistics can be disabled using +the command @code{timing} (@pxref{Configuration commands}).}. After running the program, the program counter will point to the address after the one containing the @code{HLT} instruction. In our case, asking the value of the program counter after executing the program will give us @@ -433,7 +440,7 @@ MSG: 3002 MIX > @end example -Other useful commands for debugging are @code{tron} (which turns on +Other useful commands for debugging are @code{tracing} (which turns on tracing of executed intructions) and @code{weval} (which evaluates w-expressions on the fly). For a complete description of all available MIX commands, @xref{mixvm}. |