MI Source Debugger

Hi All,

RE:  

>   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-/[email protected] 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.
>    
I wrote an MI Source Debugger a while back.  You do NOT need to code BRK statements in your program.  It has single-step run mode, a "Run-to Line Number" command (like STRISDB), and you can execute certain "Debug Commands" such as EV to Evaluate a variable at run time (not change).  You set breakpoints with F6.  The look and feel is like the standard AS/400 ILE debugger, but of  course this is for MI programs only.    There are a few minor limitations such as no embedded /*comments*/ but it works pretty well, I think.  Much easier than hand-coding BRK statements or, worse, at run time, executing ADDBKP for every place you want to stop at.   It also lets you look at the "dotted variables".  

Rich Hart
_______________________________________________
This is the MI Programming on the AS400 / iSeries (MI400) mailing list
To post a message email: MI400-Zwy7GipZuJhWk0Htik3J/[email protected]
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/mi400
or email: MI400-request-Zwy7GipZuJhWk0Htik3J/[email protected]
Before posting, please take a moment to review the archives
at http://archive.midrange.com/mi400.