Micro Focus Visual COBOL 2.3 for Eclipse (UNIX) > Welcome > Product Information > Known Issues and Restrictions > Problem Determination and Diagnostic Tools > Debugging in Eclipse

Debugging in Eclipse

The debugger ignores a COBOL watchpoint that is hit if there is no statement following the statement that modifies the data on which that watchpoint is set.
If you delete a project while you are debugging it, the delete action will only be partially successful and errors will occur. You must stop the debug process before deleting a project.
There is an issue with "Wait for attachment" when you use Visual COBOL for Eclipse to debug applications that run on some UNIX/Linux platforms. Eclipse connects to the debugger on the remote machine, but might not attach to the process to debug the code.
To work around this issue, ensure that on the remote machine the TMPDIR environment variable is unset or has the same value for both Micro Focus Visual COBOL Development Hub server and for the running process you wish to debug. The Micro Focus Visual COBOL Development Hub server is the server which you started either directly with the $COBDIR/remotedev/startrdoserver script or indirectly using the daemon which is started with the $COBDIR/remotedev/startrdodaemon script.

To check the variable used by the Micro Focus Visual COBOL Development Hub server:
1. Open Remote Systems view in Eclipse on the Windows machine.
2. Right-click the Shells element of the server connection to be tested and click Launch Shell.
3. In the Remote Shell view, type echo $TMPDIR in the Command field, and press Enter.
  The value of the TMPDIR environment variable is shown - ensure it is the same as the one used by the process to be debugged.
  
  Note: The value of TMPDIR used by the Development Hub server cannot be changed in the remote shell and must be set before you start the daemon or server.