1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
|
@c -*-texinfo-*-
@c This is part of the GNU MDK Reference Manual.
@c Copyright (C) 2000, 2001
@c Free Software Foundation, Inc.
@c See the file mdk.texi for copying conditions.
@node gmixvm, mixasm, mixvm, Top
@comment node-name, next, previous, up
@chapter @code{gmixvm}, the GTK virtual machine
@cindex @code{gmixvm}
@cindex GUI
@cindex GTK+
@menu
* Invoking @code{gmixvm}:: Invoking the GTK+ interface.
* MIXVM console:: Using @code{mixvm} commands.
* MIX virtual machine:: The MIX virtual machine window.
* MIXAL source view:: Viewing the MIXAL source code.
* MIX devices view:: Device output.
* Menu and status bars:: Available menu commands.
@end menu
@node Invoking @code{gmixvm}, MIXVM console, gmixvm, gmixvm
@comment node-name, next, previous, up
@section Invoking @code{gmixvm}
If you have built @sc{mdk} with GTK+ support (@pxref{Installing MDK}), a
graphical front-end for the MIX virtual machine will be available in
your system. You can invoke it by typing
@example
gmixvm @kbd{RET}
@end example
@noindent
at your command prompt. The @code{gmixvm} main window will appear,
offering you a graphical interface to run and debug your MIX programs.
@image{img/ss_mix}
Apart from the menu and status bars, we can distinguish two zones (or
halves) in this main window. In the upper half of @code{gmixvm}'s main
window there is a notebook with three pages, namely,
@itemize
@item
a MIX virtual machine view, which shows you the registers, flags, memory
contents and time statistics of the virtual machine;
@item
a MIXAL source view, which shows the MIXAL file and lets you manage
breakpoints;
@item
a Devices view, which shows you the output to character based MIX block
devices.
@end itemize
@noindent
The application can run in two modes: non-split (the above windows are
placed in a notebook in the main window) or split mode (the windows are
detached from the main one, and can be hidden individually). You can
choose the display mode using the menu command @w{Settings->Split
windows}.
@ifnotinfo
Here is an screenshot showing how @code{gmixvm} looks like when running
in split mode:
@image{img/ss_split}
@end ifnotinfo
On the other hand, the main window's lower half presents you a
@code{mixvm} command prompt and a logging area where results of the
issued commands are presented (in split mode, these widgets occupy the
whole main window's space between the menu and status bars). These
widgets implement a @code{mixvm} console which offers almost the same
functionality as its @acronym{CLI} counterpart.
When @code{gmixvm} is run, it creates a directory named @file{.mdk} in
your home directory (if it does not already exist). The @file{.mdk}
directory contains the program settings, the device files used by your
MIX programs (@pxref{Devices}), and a command history file.
The following sections describe the above mentioned components of
@code{gmixvm}.
@node MIXVM console, MIX virtual machine, Invoking @code{gmixvm}, gmixvm
@comment node-name, next, previous, up
@section MIXVM console
In the lower half of the @code{gmixvm} main window, you will find a
command text entry and, above it, an echo area. These widgets offer you
the same functionality as its @acronym{CLI} counterpart, @code{mixvm}
(@pxref{mixvm}). You can issue almost all @code{mixmv} commands at the
@code{gmixvm}'s command prompt in order to manipulate the MIX virtual
machine. Please refer to @xref{mixvm}, for a description of these
commands, and to @xref{Getting started}, for a tutorial on using the MIX
virtual machine. The command prompt offers command line completion for
partially typed commands using the @kbd{TAB} key; e.g., if you type
@example
lo @kbd{TAB}
@end example
@noindent
the command is automatically completed to @code{load}. If multiple
completions are available, they will be shown in the echo area. Thus,
typing
@example
p @kbd{TAB}
@end example
@noindent
will produce the following output on the echo area:
@example
Completions:
pc psym preg pflags pall
pmem
@end example
@noindent
which lists all the available commands starting with @code{p}. In
addition, the command prompt maintains a history of typed commands,
which can be recovered using the arrow up and down keys. As mentioned
above, a file containing previous sessions' commands is stored in the
configuration directory @file{~/.mdk}, and reloaded every time you start
@code{gmixvm}.
You can change the font used to display the issued commands and the
messages in the echo area using the @w{Settings->Change font->Command
prompt} and @w{Settings->Change font->Command log} menu commands.
@node MIX virtual machine, MIXAL source view, MIXVM console, gmixvm
@comment node-name, next, previous, up
@section MIX virtual machine
The first notebook's page displays the current status of the virtual
machine. There you can find the registers' contents, the value of the
comparison and overflow flags, the location pointer, a list with all MIX
memory cells and their contents, and the time statistics (including
total uptime, elapsed time since the last run command and total
execution time for the currently loaded MIX program).
Clicking any register entry, you will be prompted for a new register's
contents.
@ifnotinfo
The next figure shows the enter word dialog.
@image{img/ss_worddlg, 400pt}
@end ifnotinfo
In the same manner, click on any address of the memory cells list to be
prompted for the new contents of the clicked cell. If you click the
address column's title, a dialog asking you for a memory address will
appear; if you introduce a valid address, this will be the first cell
displayed in the scrollable list after you click the OK button.
@ifnotinfo
The next figure shows the enter address dialog.
@image{img/ss_goto}
@end ifnotinfo
The register contents are shown as a list of MIX bytes plus sign. If you
place the mouse pointer over any of them, the decimal value of this MIX
word will appear inside a tooltip.
You can change the font used to display the MIX virtual machine contents
using the @w{Settings->Change font->MIX} menu command.
@node MIXAL source view, MIX devices view, MIX virtual machine, gmixvm
@comment node-name, next, previous, up
@section MIXAL source view
The second notebook's page, dubbed MIXAL, shows you the MIXAL source of
the currently loaded MIX file. As shown in the next figure, the
information is presented in two columns.
@image{img/ss_mixal, 400pt}
The first column shows the address and memory contents of the compiled
MIX instruction, while the second one displays its corresponding MIXAL
representation, together with the source file line number. The current
location of the location counter is highlighted in grey, while any set
breakpoint is marked in red. You can set/unset breakpoints by clicking
on any line in this view which has an associated memory address.
The colors used to mark the location pointer line and the breakpoints
can be customized with the @w{Settings->Colors...} menu command. When you
click on this menu item, a dialog showing the current line colors will
appear.
@ifnotinfo
The following figure shows the change color dialog.
@image{img/ss_colors}
@end ifnotinfo
Clicking on any of the colors will produce a color selection dialog for
choosing a new color for the given element. In this way, you can change
the foreground and background colors used for drawing the current line,
the lines where breakpoints have been set and plain MIXAL code lines.
You can change the font used to display the MIXAL source code
using the @w{Settings->Change font->MIXAL} menu command.
@node MIX devices view, Menu and status bars, MIXAL source view, gmixvm
@comment node-name, next, previous, up
@section MIX devices view
The last notebook page, dubbed Devices, shows you the output/input
to/from MIX block devices (the console, line printer, paper tape,
disks, card and tapes @pxref{Devices}) produced by the running
program.
@ifnotinfo
@image{img/ss_devices, 400pt}
@end ifnotinfo
Input device contents is read from files located in the @file{~/.gmivm}
directory, and the output is also written in files at the same
location. Note that device tabs will appear as they are used by the MIX
program being run, and that loading a new MIX program will close all
previously open devices.
The input/output for binary block devices (tapes and disks) shall be a
list of MIX words, which can be displayed either in decimal or word
format (e.g. @w{- 67} or @w{- 00 00 00 01 03}. The format used by
@code{gmixvm} can be configured using the @w{Settings->Device output}
menu command for each binary device.
You can change the font used to display the devices content
using the @w{Settings->Change font->Devices} menu command.
@node Menu and status bars, , MIX devices view, gmixvm
@comment node-name, next, previous, up
@section Menu and status bars
The menu bar gives you access to the following commands:
@deffn File Load...
Opens a file dialog that lets you specify a binary MIX file to be loaded
in the virtual machine's memory. It is equivalent to the @code{mixvm}'s
@code{load} command (@pxref{File commands}).
@end deffn
@deffn File Edit...
Opens a file dialog that lets your specify a MIXAL source file to be
edited. It is equivalent to the @code{mixvm}'s @code{edit} command
(@pxref{File commands}). The program used for editing can be specified
using the menu entry @code{@w{Settings->External programs}}.
@end deffn
@deffn File Compile...
Opens a file dialog that lets your specify a MIXAL source file to be
compiled. It is equivalent to the @code{mixvm}'s @code{compile} command
(@pxref{File commands}). The command used for compiling can be specified
using the menu entry @code{@w{Settings->External programs}}.
@end deffn
@deffn File Exit
Exits the application.
@end deffn
@deffn Debug Run
Runs the currently loaded MIX program, up to the next breakpoint. It is
equivalent to the @code{mixvm}'s @code{run} command (@pxref{Debug
commands}).
@end deffn
@deffn View MIX
@deffnx View MIXAL
@deffnx View Devices
These toggles are available when running @code{gmixvm} in split mode,
and let you turn on/off the visibility of the corresponding
@code{gmixvm} windows.
@end deffn
@deffn Debug Next
Executes the next MIX instruction. It is equivalent to the
@code{mixvm}'s @code{next} command (@pxref{Debug commands}).
@end deffn
@deffn Debug @w{Clear breakpoints}
Clears all currently set breakpoints. It is equivalent to the
@code{mixvm}'s @code{cabp} command.
@end deffn
@deffn Debug Symbols...
Opens a dialog showing the list of symbols defined in the currently
loaded MIX program.
@ifnotinfo
@image{img/ss_symbols}
@end ifnotinfo
@end deffn
@deffn Settings Colors...
Lets you change the colors used to mark the current and breakpoint lines
in the MIXAL tab, as well as the colors used for plain source lines.
@end deffn
@deffn Settings @w{Change font}
Lets you change the font used in the various @code{gmixv} widgets
(i.e. commad prompt, command log, MIX, MIXAL and devices).
@end deffn
@deffn Settings @w{Device output...}
Opens a dialog that lets you specify which format shall be used to show
the contents of MIX binary block devices.
@ifnotinfo
@image{img/ss_devform}
@end ifnotinfo
The available formats are decimal (e.g. @w{-1234}) and MIX word
(e.g. @w{- 00 00 00 19 18}).
@end deffn
@deffn Settings @w{Devices dir...}
Opens a dialog that lets you choose where the MIX device files will be
stored (@file{~/.mdk} is the default location).
@ifnotinfo
@image{img/ss_devdir}
@end ifnotinfo
You can also specify the devices directory using the @code{mixvm}
command @code{devdir} (@pxref{Configuration commands}).
@end deffn
@deffn Settings @w{External programs...}
This menu command opens a dialog that lets you specify the commands used
for editing and compiling MIXAL source files.
@ifnotinfo
@image{img/ss_extprog}
@end ifnotinfo
The commands are specified as template strings, where the control
substring @code{%s} will be substituted by the actual file name. Thus,
if you want to edit programs using @code{vi} running in an @code{xterm},
you must enter the command template @code{@w{xterm -e vi %s}} in the
corresponding dialog entry. These settings can also be changed using the
@code{mixvm} commands @code{sedit} and @code{sasm} (@pxref{Configuration
commands}).
@end deffn
@deffn Settings Save
Saves the current settings.
@end deffn
@deffn Settins @w{Save on exit}
Mark this checkbox if you want @code{gmixvm} to save its settings
every time you quit the program.
@end deffn
@deffn Help About...
Shows information about @code{gmixvm}'s version and copyright.
@end deffn
On the other hand, the status bar displays the name of the last loaded
MIX file. In addition, when the mouse pointer is over a MIXAL source
file line that contains symbols, a list of these symbols with their
values will appear in the status bar.
|