Debugger info file cannot be located. Cannot proceed to debug application

[stanjest]

I have been developing apps on this system for over 5 years. Recently, the CVI LabWindows Ver 6.0 started popping up this message that the debugging information file cannot be located. It gives you a option to proceed without the debugging features or ABORT or browse for the cdb file. Even if you browse for the file, it would come back with a message that the file is out of date.

The work around that I have found is to delete the cdb and the debug exe file and RUN the app from the interactive windows. This will work like normal. But the question is why is this situation popping up now. and why is it that I would need to physically blow away the 2 file before it would work? Note that I am developing the app from a server. ie all the file are located on the server. The server status has not change recently.

Regards

Steven

[AEDavid]

Hi Steven,

Did you change any of the debugging options before running when the error appeared?  If so, it may need to change the .cdb file to include additional information.  Also, you do not need to delete the .cdb file first - you can simply select Build >> Create Debuggable Executable and it will overwrite it.

[stanjest]

I did not change the build option. It was the same as before.

You were right I do not need to delete the cdb file. But I have the delete the dbg.exe file.

That would force it to re-create the dbg.exe file and it would work for that session. After that session is over, I touch the code, re-compile, build another dbg.exe (without deleting the current version physically) and according to the date and time stamp on the file, it is the latest version, it will not work. The cannot file debug info message pop-up.

What is the syning mechanism the determine when this debug info message pop up?

Regards

Steven

[AEDavid]

Hi Steven,

1. Are you calling any dlls from your executable?  If so, please search the CVI help for .cdb.  The Debugging DLLs document should provide some insight into this situation.  It may be that CVI is looking for the debug info for the dll, not the exe. 
2. Please search your hard drive for any other copies of the project name .cdb.  It may be finding another version than what you are expecting. For more info on this, please see the help article Location of Files Required for Debugging DLLs.
3. Finally, I am a little unclear when you say build another dbg.exe, are you referring to Build >> Create Debuggable Executable?  This should always overwrite both the .cdb and .exe.