topic Hello, in Analyzers

Advisor XE 2016 Analysis fail when loading managed .NET assembly

Alain_M_ — Tue, 17 May 2016 15:26:05 GMT

We have a C++/C# software that we profile with Advisor XE 2016.

During profiling session, when we load a .NET assembly, Advisor stops "Check Dependencies" analysis with the message :

"Failed to load .NET profiler, please reinstall Advisor".

The problem is that I want to profile only C++ native modules, not the C# ones ... and I don't see a .NET profiler in Advisor.

Kirill_R_Intel — Tue, 17 May 2016 16:12:15 GMT

Hello,

Try to change "managed code profiling mode" in Advisor project properties to "native", to disable .NET profiling.

Regards,
Kirill

Kirill_R_Intel — Mon, 23 May 2016 09:55:14 GMT

If native mode doesn't help, would you be able to provide your application executable, so that I can reproduce the problem?

Alain_M_ — Tue, 24 May 2016 07:54:17 GMT

Hello,

Native mode doesn't help.

As our application is very big, we cannot provide it to you. I will try to reproduce the problem with a small sample including a C++/CLI assembly.

Regards.

Alain.

Alain_M_ — Fri, 27 May 2016 15:12:01 GMT

Hello,

I have successfully reproduced the problem with a main exe module in native C++ and a C++/CLI DLL.

I have joined the VS 2012 solution to the post. I use .NET Framerwork 4.0.

When Advisor (Check Dependencies) or even Inspector (Thread and Memory Profiling) try to load the managed DLL, the profiler is crashing.

Alain_M_ — Fri, 27 May 2016 15:14:07 GMT

I just wanted to precise that the crash occurs in Release mode, not in Debug mode.

Regards.

Alain.

Kirill_R_Intel — Fri, 27 May 2016 15:56:17 GMT

Thank you Alain for the reproducer! I see the problem and submitted a bug tracker to development team.

Kirill_R_Intel — Wed, 20 Jul 2016 10:21:36 GMT

Alain, this bug was fixed in Intel Inspector 2017, that should be released in August-September. Thank you for reporting the issue!