Skip to main content

I've been working on using udb (https://undo.io/) with native COBOL using Visual Studio code. So far it works ok as I can step forward and backward over code.

The problem is that I can't see any of the variables. I suspect this is because the executables don't contain any of the DWARF information used by most debuggers but instead use seperate .idy files

I can see that you do support this for Visual COBOL and Eclipse (www.microfocus.com/.../time-travel-debug-extension-for-visual-cobol-and-enterprise-developer) and would like to extend that functionality to Visual Studio Code.

I see that this is supported by IBM via the TEST(DWARF) compiler option (www.ibm.com/.../6.1 and was wondering if Opentext had something similar

Currently using Micro Focus Visual COBOL Development Hub 8.0 but I can upgrade to 9.0 if you believe that will make a difference

Thank you in advance for your help.

I've been working on using udb (https://undo.io/) with native COBOL using Visual Studio code. So far it works ok as I can step forward and backward over code.

The problem is that I can't see any of the variables. I suspect this is because the executables don't contain any of the DWARF information used by most debuggers but instead use seperate .idy files

I can see that you do support this for Visual COBOL and Eclipse (www.microfocus.com/.../time-travel-debug-extension-for-visual-cobol-and-enterprise-developer) and would like to extend that functionality to Visual Studio Code.

I see that this is supported by IBM via the TEST(DWARF) compiler option (www.ibm.com/.../6.1 and was wondering if Opentext had something similar

Currently using Micro Focus Visual COBOL Development Hub 8.0 but I can upgrade to 9.0 if you believe that will make a difference

Thank you in advance for your help.

Hi Daniel,

 

Thank you for your interest in using the Reverse Debugging feature in Visual COBOL. I've passed along your question, and one of my colleagues from OpenText will be contacting you to discuss this question further.

Terms & ConditionsAccessibility statement