Starting with a version 1.4 does not have standard ST
screen parameters embedded into its code. Instead it reads all
necessary information from line-A variables and reserves all needed
buffers accordingly. In particular it follows that will
run correctly in all six TT resolutions. It may also work with
different overscan utilities, provided screen geometry variables
in a machine were updated properly. Note that fonts used are
resolution dependent but fixed for a given resolution. This means
that putting monochrome ST into 50 line mode will not give nice
results without code modifications (see w_init()
in
window.c).
A special support is provided for Moniterm monitors. Because of limitations of a Moniterm driver you will need also a standard ST monitor connected in parallel. In such setup your program screen will be displayed on Moniterm and will print its information to a side monitor; no screen flipping with W is needed or possible.
Since the debugger tries to limit use of a dynamic memory allocations the code which reserves work screen and necessary buffers does that in a ``false'' program space and is located in start.s. Should you decide to modify it for any reasons look for comments which attempt to describe what really happens.
Note: despite of the fact that can be used on TT the version 1.4 is still ST debugger in that sense that it does not support yet any of 68020/30 specific codes. This should be fine for most programs in the nearest future. An expansion will be easy and straightforward provided you will have necessary reference handy.