Mon, 08/05/2024 - 12:26
Forums:
I built it based on OCCProxy When I successfully build and run a NET/C++hybrid programming project (refer to the tutorial for. NET: Import/Export (C # | C++/CLI | WinForms | WPF)), all other behaviors of the program are normal, but I cannot view the values of OCCProxy's variables (including local and member variables).
When I click on a variable and right-click to select 'Add Monitor', the monitoring window displays' C++Compiler Internal Error 'in the value area of the variable.
I consulted the manual of Visual Studio, checked my project properties, and found that the settings meet the requirements of the manual. May I ask what other possible reasons could be causing it? How should I try to solve this problem?
Wed, 08/07/2024 - 13:35
I consider that you have already built OCCTProxy and OCCT itself in Debug mode, and trying to run application in environment, where PDB files are available to debugger (check the debugger log to see if it is able to load debugging symbols for related DLL libraries).
Apart from this, VisualStudio by default provides debugging of either managed code (e.g. C#) or native code (C++). And it is necessary to explicitly set in debugger setting to debug both at once (the location of this setting moved between different versions of VisualStudio - try to search info for your version). I might be wrong, but this option might be also unavailable for limited versions of VisualStudio (like Express or Community edition), but I've worked with these things too long time ago.
Tue, 08/13/2024 - 09:40
Thank you for your answer! I've found the reason!
My company installed an encryption system on office computers and implemented some customized supervision policies for the development software Visual Studio, which inadvertently caused this problem (I don't understand the root cause, after all, I am not the person who made this encryption system). After contacting the encryption system vendor to modify some policies, the problem disappeared.
Ordinary users should not encounter this problem when building OCCT projects on personal computers.