Paul Jackson wrote:
this was code that I obtained from Tim McCarthy when he was at Trailblazer
systems ca. 1996. I've never debugged an MI program before. Any tips on
how to do this?
To begin with, you need a compilation listing. Debugging is through the
OPM debugger, by hexadecimal instruction number; all variables can be
accessed through DSPPGMVAR unless their names start with periods.
When setting breakpoints, use the instruction number (I don't have a
compilation listing in front of me, but I believe it's the second
column, the one that shows an ascending sequence of hexadecimal
numbers). For example, if the instruction of interest is at instruction
number 002D, then you would set your breakpoint at '/002D' (including
the slash and the single quotes, to tell the debugger that you want an
instruction number rather than a HLL statement number).
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.