Debugging Native COBOL Link Libraries
You can directly debug Link Library projects that produce a single .dll file, whereas for Link Library projects which produce multiple .dll files you must specify one of the output .dll files (or an executable which loads it) in the "Start external program" option on the Debug tab in your project properties.
Wait for Debuggable Attachment and Native COBOL
When you use Wait for debuggable attachment the debugger waits for the program to start in a separate process before attempting to attach to it.
Using COBOL Watchpoints and Break on Data Change in Native COBOL
Native code applications can cause memory overflows by occasionally writing in memory when they should not. You might not be able to locate the line of code that is responsible for the overflow and the only way to find the problem is to watch the area of memory.
