Rocket U2 | UniVerse & UniData

I am stepping through code and to avoid long subroutine calls, I do a  "BLnnnn"  in the BASIC Debugger where nnnn is a line after the subroutine call I want to 'blip through' -- more often than not now, the BL command is met with a minidump:

And this happens in LOTS of places -- why is the BASIC debugger doing this now, and is this new to this release?

I am having to resort to coding in "DEBUG" or PRINT xxx/ INPUT WAIT into the code, which just means I have to take it all out later.

AND it is not EVERY use of "BL" - just in some cases which I cannot identity the 'why' part -- sometimes it works, many times it MINIDUMPS.

Any thoughts welcome -- I don't know how to make this 'happen' in a way I can hand off in a support case to Rocket -- if there are thoughts there, glad to hear those as well.

I feel accomplished, as I have generated over a dozen MiniDumps in the last hour.  A new personal best.  :eyeroll:   :-)

------------------------------
David Wolverton
Independent
Sunset Programming Inc
Waltham MA US
------------------------------

I am stepping through code and to avoid long subroutine calls, I do a  "BLnnnn"  in the BASIC Debugger where nnnn is a line after the subroutine call I want to 'blip through' -- more often than not now, the BL command is met with a minidump:

And this happens in LOTS of places -- why is the BASIC debugger doing this now, and is this new to this release?

I am having to resort to coding in "DEBUG" or PRINT xxx/ INPUT WAIT into the code, which just means I have to take it all out later.

AND it is not EVERY use of "BL" - just in some cases which I cannot identity the 'why' part -- sometimes it works, many times it MINIDUMPS.

Any thoughts welcome -- I don't know how to make this 'happen' in a way I can hand off in a support case to Rocket -- if there are thoughts there, glad to hear those as well.

I feel accomplished, as I have generated over a dozen MiniDumps in the last hour.  A new personal best.  :eyeroll:   :-)

Not that this is an answer to the minidump problem, but when I am debugging and want to "blip" through subroutine calls (which is often, since I don't have source for vendor supplied code), I use "N1 R" from the debugger, to "step over" a line of code every time ENTER is pressed.

The dump is definitely not right, but perhaps N1 R could be a workaround in the meantime?

I am stepping through code and to avoid long subroutine calls, I do a  "BLnnnn"  in the BASIC Debugger where nnnn is a line after the subroutine call I want to 'blip through' -- more often than not now, the BL command is met with a minidump:

And this happens in LOTS of places -- why is the BASIC debugger doing this now, and is this new to this release?

I am having to resort to coding in "DEBUG" or PRINT xxx/ INPUT WAIT into the code, which just means I have to take it all out later.

AND it is not EVERY use of "BL" - just in some cases which I cannot identity the 'why' part -- sometimes it works, many times it MINIDUMPS.

Any thoughts welcome -- I don't know how to make this 'happen' in a way I can hand off in a support case to Rocket -- if there are thoughts there, glad to hear those as well.

I feel accomplished, as I have generated over a dozen MiniDumps in the last hour.  A new personal best.  :eyeroll:   :-)

Ian, is N1 R the same as E1 R or is there a difference?

Not that this is an answer to the minidump problem, but when I am debugging and want to "blip" through subroutine calls (which is often, since I don't have source for vendor supplied code), I use "N1 R" from the debugger, to "step over" a line of code every time ENTER is pressed.

The dump is definitely not right, but perhaps N1 R could be a workaround in the meantime?

I am stepping through code and to avoid long subroutine calls, I do a  "BLnnnn"  in the BASIC Debugger where nnnn is a line after the subroutine call I want to 'blip through' -- more often than not now, the BL command is met with a minidump:

And this happens in LOTS of places -- why is the BASIC debugger doing this now, and is this new to this release?

I am having to resort to coding in "DEBUG" or PRINT xxx/ INPUT WAIT into the code, which just means I have to take it all out later.

AND it is not EVERY use of "BL" - just in some cases which I cannot identity the 'why' part -- sometimes it works, many times it MINIDUMPS.

Any thoughts welcome -- I don't know how to make this 'happen' in a way I can hand off in a support case to Rocket -- if there are thoughts there, glad to hear those as well.

I feel accomplished, as I have generated over a dozen MiniDumps in the last hour.  A new personal best.  :eyeroll:   :-)

Kevin, both execute the current line; the only difference is that "E" steps into subroutine calls (F11 in VS), but "N" steps over them (F10), which is super helpful when you don't have the source code for all subroutines and "V"iew source is on.  Using "E1 R", I end up in a subroutine, have to do V to turn off view source, OUT to return back to the main program, then V to turn view source back on.

The past few years I've been trying to get better at using the debugger, and get away from liberally sprinkling CRT statements all over my programs :-) . I do sometimes emulate log4j and have e.g. LOGLEVEL=3 at the top, and have print statements like "IF LOGLEVEL>1 THEN CRT \BLAH BLAH\", which lets me turn the dial on how much logging to have.

Really looking forward to having a visual debugger in the VSCode extension!

Ian, is N1 R the same as E1 R or is there a difference?

Not that this is an answer to the minidump problem, but when I am debugging and want to "blip" through subroutine calls (which is often, since I don't have source for vendor supplied code), I use "N1 R" from the debugger, to "step over" a line of code every time ENTER is pressed.

The dump is definitely not right, but perhaps N1 R could be a workaround in the meantime?

I am stepping through code and to avoid long subroutine calls, I do a  "BLnnnn"  in the BASIC Debugger where nnnn is a line after the subroutine call I want to 'blip through' -- more often than not now, the BL command is met with a minidump:

And this happens in LOTS of places -- why is the BASIC debugger doing this now, and is this new to this release?

I am having to resort to coding in "DEBUG" or PRINT xxx/ INPUT WAIT into the code, which just means I have to take it all out later.

AND it is not EVERY use of "BL" - just in some cases which I cannot identity the 'why' part -- sometimes it works, many times it MINIDUMPS.

Any thoughts welcome -- I don't know how to make this 'happen' in a way I can hand off in a support case to Rocket -- if there are thoughts there, glad to hear those as well.

I feel accomplished, as I have generated over a dozen MiniDumps in the last hour.  A new personal best.  :eyeroll:   :-)