LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

An error occured while loading debugging information

When I try to run my project in debug mode, I get this error message:

 

"An error occurred while loading debugging information for '[path]\name_dbg.exe'. You will be unable to debug this DLL\EXE.

If this DLL/EXE was built with an earlier version of LabWindows/CVI you might have to rebuild it using this version.

Would you like to terminate execution?' [Yes/No]

 

We are facing this issue in atleast 5 machines in which we have CVI. I am using LabWindows CVI 2010 SP1. 

 

Initially, this problem used to be intermittent, meaning CVI used to give this error only once in a while. Then, it started giving error every time we hit 'run' in debug mode. In those situations, closing and launching CVI used to make the error disappear till the next compilation. But since last week, CVI in one of the machines started giving this message all the time. Only way to make it go away is to rebuild the whole project, which takes almost 10 minutes. The error dialog will reappear as soon as we compile the project again. 

 

If I hit 'No' in the error dialog, the application will launch, but I will not be able to debug.

 

I would like to share the project, but unfortunately, I cannot do that. Any help in resolving this will be greatly appreciated.

 

Error Dialog

0 Kudos
Message 1 of 4
(4,915 Views)

If your project is taking 10 minutes to build, I am thinking that this is a memory issue dealing with such a huge project. How much memory is cvi.exe using when this error appears? One thing you can do to reduce the memory during debug is to disable some files which you do not need debugging info for. Use the Disable/Enable .Obj option to turn off the debugging info on particular files in your project. You can also disable the Generate source code browse information option in the Build Option, or also reduce the Debugging level.

 

These options are really workaround, but if they do work, then it does point to a memory issue.

National Instruments
Message 2 of 4
(3,764 Views)

Hi,

I am also facing simillar issues on my machine, but not same. Did you solve this problem. Please let me know if you got solution.

0 Kudos
Message 3 of 4
(3,744 Views)

Sorry for this delay, some how missed the post.

 

As D Biel pointed out, I disabled 'Generate source code browse information option'. This seems to have solved the problem. After disabling this option, we have not faced the issue for the last 1.5 months.

0 Kudos
Message 4 of 4
(3,681 Views)