i have parallel 2013. the release notes says Inspector and Advisor are included. how do i start them and is there a user guide/ thx
Is it possible to install an evaluation of Intel Inspector XE 2015 on Linux without root access? I usually just use it on Windows, and I'm just evaluating it on Linux, so I don't want to bother system administrators unless the evaluation proves successful. Can someone please email me a license file? As far as I can tell my purchased Windows license file won't work for a Linux install.
I'm trying to attach my debugger to see a data race in the act, but I can't find the context menu item "Debug This Problem" explained in the documentation "About Investigating Problems Using Interactive Debugging" ( https://software.intel.com/en-us/node/528095 ):
I am running inspector on the OmpScr benchmark. The benchmark allow you to specify a problem size for each of the programs. When I run inspector using small size problem it is able to finish the verification process most of the time but for some of the problem (i.e. c_loopB.badSolution1.par). I get the error:
Error: Internal error. Please contact Intel customer support team.
What does "Use maximum resources" option do on the data race detection analysis?
I found that there is a significant performance differcence between with and without that option. But the analysis results are not quite different.
For instance, for one program it took about 15 seconds without the option while it took about 5 minutes with the option.
Does it make skip analysis for some parts of a program? Some kind of sampling technique?
I tried to use Intel Inspector (from XE 2015) with little success. The application I try to analyze uses boost threads and a boost spirit parser. Thread safety defines have been added (eg BOOST_SPIRIT_THREADSAFE).
The following example displays the problem. In normal Release/Debug builds the program will output :
If Intel Inspector XE 2015 is used with "Thread Error Analysis" the program fails with stack corruption during the execution of boost::call_once.
I am working with Inspector XE2015 integrated with Visual Studio 2012.
Inspector has helped me to find uninitialized variable. I want to use debugger in the moment when this error occurs. However when I start Inspector in one of modes "Enable debugger when problem detected" or "Select analysis start location with debugger" all crashes: first the debugged program, then the inspector, and at last the Visual Studio.
What conditions did not I follow to have a success with this matter?
When I try to run any of the 3 analyses available in Inspector I get the error "Severe (157): Program Exception - access violation" and the line with the call of "omp_get_num_procs" is listed in the console output:
use omp_lib integer*4 procs procs = omp_get_num_procs ( )
I double checked that I use following settings in my project: /debug:full, /Od, /check:none, /libs:dll /threads /dbglibs (Debug Multithread DLLs), /Qopenmp.
I find our application becomes very slow, then always has no response,when Use the Intel Inspector XE to coolect the memory leaks or thread errors.
Who met this kind of phenomenon？how I should Set the something?
- Página 1