Re: MI source debugger

[Keith Carpenter <entropypool@xxxxxxxxx>]

diego acevedo wrote:
> Hi, everyone:
>   Since I couldn't find a MI interactive source debugger (like STISDB), I've decide to write my own.
>    
>   It is not a professional one but makes its job reasonably well. The only "problem" is that you have to insert many BRK's clause (one after executable line) or at least, in those places you want to check in the source code.
>    
>   When the MI program is running, the display highlights the statement executed and you can peek or change the value of variables.
>    
>   If someone is interested in use my debugger, please ask me to diegomacevedo@xxxxxxxxxxxx and I'll send you. This program can be modified at will to, for instance, add new features or fix any "bug". The only condition I ask you is to share such modifications.
>    
>   Thank you!
>   Diego M. ACEVEDO
>    
>   ps: The .zip contains a Readme.txt file with the help to use this program; this file was written in spanish :(  -Sorry, I'm argentinian!
>    

Actually, you might be able to use ISDB with plain MI programs. I used 
to work for a place that had a tool that modified the RPG generated IRP 
source before passing it to the MI compiler.  Kind of neat way to inline 
MI inside of an RPG program.  It's better to use MI built-ins today, but 
this was years ago.

The trick with using ISDB with these hybrid MI programs was to change 
the program attribute from blank (or whatever your MI compiler uses) to 
RPG.  ISDB only works on OPM programs with a known attribute.   You 
still need to add all the BRK statements if you want to debug at the 
statement level.

Modifying the program attribute is bit more restricted these days. It's 
actually part of the library OIR and not the program.


Keith