Connection with the debug engine was lost
Save us time! Click 'Report an Issue' from the Help and Support panel inside of VS Code after you have connected to a system.
Describe the bug Debugging an RPGLE source, which I successfully debugged all the way through a few minutes ago. Now the debug engine connection gets lost on the 2nd step after stepping through once.
To Reproduce Steps to reproduce the behavior: Debugging a SQLRPGLE source member. went away for a while and came back. debugged again and now it can't debug through.
Expected behavior Should debug all the way through without losing connection to debug engine
Video
Environment (please complete the following information):
- Extension version IBM i Debug v1.0.0 Code for IBM i v2.3.1
- IBM i OS version 7.4
Additional context Add any other context about the problem here.
Can you attach the output of the debug service here? The debug service output either appears at the debug service green screen console, or a QPRINT file for a JVM process, depending on how you start debug service.
It seems to be running in a JVM service but I'm not sure how to get the output from it? Not much in its job log and no spool files.... Where is output written to?
job log entries:
Java Virtual Machine is IBM Technology for Java. PID(834)
JVM properties were loaded from a properties file.
NO spool files output
There is a FAQ on this in the Merlin debug doc link (https://www.ibm.com/docs/en/merlin/1.0?topic=environment-debugging):
Question: How can I see the output of the debug service? Answer: You can see the output of IBM i Debug Service from the QPRINT file at the output queue QUSRSYS/QDBGSRV. You may need to stop the debug service before inspecting the content of the QPRINT file.
If you use RDi, the QPRINT file will appear under the Spool Files filter.