Debugging Visual Cobol GUI class from a core dump file

0 Likes
over 2 years ago

Problem:

When debugging an application using a core dump from cblcore, the Visual Cobol GUI class library is seen as part of the call stack.

How can this be debugged?

 

Resolution:

The GUI class IDY files are needed in order to debug, so the class needs to be compiled to produce them.

  • Copy the "guicl" folder located in the directory below, into another directory.

C:\Program Files (x86)\Micro Focus\Visual COBOL\cpylib\guicl\

  • Open the contained project apiguim.cblproj with VCVS and compile it.

 

If windows.cpy is missing, search for it in C:\Program Files (x86)\Micro Focus\Visual COBOL\cpylib and copy it into the project directory.

 

If the compilation gives error

"LINK : fatal error LNK1181: cannot open input file 'imm32.lib'",

make sure the IDE can find the following files:

  • comctl32.lib
  • comdlg32.lib
  • shell32.lib

For a Windows 10 machine, they are located in the following directory:

C:\Program Files (x86)\Windows Kits\10\Lib\10.0.16299.0\um\x86

The steps below describe how to link them in the project:

  • On the Solution Explorer, open the Project Properties.
  • Navigate to the COBOL Link tab and in the “Link with libs” field
  • Enter the absolute paths to those libs (For Windows 10, these would be):

"C:\Program Files (x86)\Windows Kits\10\Lib\10.0.16299.0\um\x86\Imm32.Lib" 

"C:\Program Files (x86)\Windows Kits\10\Lib\10.0.16299.0\um\x86\ComCtl32.Lib" 

"C:\Program Files (x86)\Windows Kits\10\Lib\10.0.16299.0\um\x86\ComDlg32.Lib" 

"C:\Program Files (x86)\Windows Kits\10\Lib\10.0.16299.0\um\x86\shell32.lib"

  • Save the changes and Rebuild the Solution.
Comment List
Anonymous
Related Discussions
Recommended