Error problem "The debugging information is out of date"

[Igor_SE]

Hello,

I am developing DLLs for automatic set-up for testing. Each function in the DLL is a test.

I have some program that runs this DLLs (program name TE). In the last station that I started to develop new DLL I have an error that doesn’t allow me to debug the DLL.

 

If I try to debug the same project on other computer there is no problems.

Could you please tell me what I am doing wrong ?

 P.S I added the error in the picture. 

BR,

Igor.M

[Al_S]

Igor:

If you are developing on multiple PCs and copy just the updated source files to the second PC, any existing debug files on that PC no longer match the source file.

You just need to rebuild your DLL project on the second PC.  In your DLL project directory, delete the DLL's .cdb file and the cvibuild directory.  On the Build menu (CVI 9.01), select Mark Project for Compilation.  From the Build menu, select Create Debuggable Dynamic Link Library.

[Igor_SE]

Thank you for your fast response.

But the development process was done on the same PC, and I already tried to delete the .cdb files

(and i dosent solve the problem)

Could you advice me what can I check all how can I solve the problem.

Thank you,

Igor.M

[Al_S]

Did you also delete the cvibuild directory, mark the project for compilation, and rebuild the debuggable DLL?  Did you get any errors or warnings during the build process?

Are you developing the calling EXE or is it an off-the-shelf test executive?

Are you sure that you deleted the .cdb file for the DLL project and not for the calling EXE project?

During your debug session, do you have the DLL project open or the calling EXE project open?

If you have the DLL project open, are you sure you have the connection between the DLL and the Executable to Debug correctly defined?

Does your calling EXE link to the DLL statically (using the .lib file) or dynamically (using LoadLibrary and GetProcAddress)?

Does the file name tst4.tmp mean anything to you?

Were you able to debug the DLL originally?

What version of CVI are you using?

[m-a]

Be sure not to have two projects generate the same .cdb files, as for instance, if you have one DLL and one test or application program using the same name.  If you generate example.dll and example.exe, the build of example.dll would generate example.cdb. Building example.exe later would overwrite the example.cdb generated by the DLL earlier - so you may need to rename the program to build.

[Kyle_M]

M-a,

While we always are pleased to see recommendations added to discussions, we do request that you do not bump very old threads. If it is a new issue similar to the prior one, please create a new thread and reference the old one in the body of the post. 

Regards,

Kyle Mozdzyn

Applications Engineering

National Instruments