Debugger isn't working as usual. (AREV Specific)
At 05 SEP 2002 06:11:27PM Michael Slack wrote:
We have AREV 3.12 on an NT network. I'm trying to use the Debugger to find a problem in a program. The problem is that as I follow line by line, the code isn't being executed in the proper way.
The DEBUG statement is in a program that deletes a row from a table. We have an MFS that will deal with rows from ceartin tables that have been deleted by coping them to a holding table. This is a safey, just in case those rows need to be recovered.
I have the DEBUG statement a couple of lines above the R/BASIC DELETE command. When the debug screen comes up I set ST (Source Trace to on) and I set E1 (show one line at a time). The delete statement seems to be executed just fine. I'm then going thru the MFS line by line. Once I get into the actual MFS executable code, it seems to just fall thru the code. I doesn't go to an internal subroutine when it hits a GOSUB (I've checked that the subroutine exists and is spelled the same). It even goes right thru a RETURN without stopping.
Any suggestions on what I might look at to get the DEBUG working properly again?
Thanks,
Michael Slack
At 05 SEP 2002 07:19PM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
Michael, you might like to post your code here.
We've seen code where variables like REM have been used, or labels match reserved keywords, and the compiler creates the code different to the programmer's expectations.
Otherwise, maybe you're out of memory? The debugger, after all, is just another program loaded AFTER your other routines.
Have you tried BLISTing the program to check the indentation???
Does the program compilation report the same number of lines as you have in your program in the editor? (ie. your program perhaps has an extra END or RETURN which is making the compilation stop prematurely -ignoring code at the bottom of the page?)
If possible, try imbedding your GOSUB code back into its calling code and try again…
World Leaders in all things RevSoft
At 06 SEP 2002 03:19PM Victor Engel wrote:
Are you certain the MFS source you have matches the object code you're running? Could you perhaps have compiled the MFS using a precompiler that somehow changed the line numbers (by, for example, reformatting the code before passing to the compiler)? Have you tried putting debugs directly in your MFS code?
At 06 SEP 2002 06:01PM Warren wrote:
Was the mfs compiled with the (L or C) options? Add a LINEMARK statement to the source code and recompile.
Was the MFS object code copied to the VERBS/SYSOBJ file (so it would be loaded into memory during intialization time for faster processing)? If this is the case most likely source code is not available for the ST option in the debugger. Use the debugger SO command if you have the source in another file. Most likely the symbol table is not present either in the VERBS/SYSOBJ.