Highlighted
Absent Member.
Absent Member.
970 views

Visual Cobol 2.3 update 2

Hi,


Recently i have noticed a issue with debug option in VC 2.3. I am able to debug code line by line in winform (code behind) but visual studio just skips the debug pointer to next statement during call to unmanaged cobol program. Unmanaged code was executed just that visual studio do not debug line by line.

This happened after i have upgraded Visual cobol 2.2 to 2.3 update 2. VC 2.2 use to debug called programs as well, i mean line by line execution.  

I have verified my debug setting and everything looks good.

Tags (1)
0 Likes
1 Reply
Highlighted
Micro Focus Expert
Micro Focus Expert

RE: Visual Cobol 2.3 update 2

The behavior you describe has always been the case with Visual COBOL and has nothing to do with upgrading to 2.3 update 2.

If you are calling an unmanaged program from a managed program then you can debug either the managed side or the unmanaged side but you cannot step from one into the other.

You can debug through the unmanaged code by setting the unmanaged project to be the Startup project and then on the debug tab point to the managed executable as your starting program. When you start debugging it will run through the managed code and stop ion the unmanaged program and you can step through at that point.

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.