Intel® Inspector XE

Uninitialized memory access

Hi, I am getting an uninitialized memory access error when profiling a C++ code with Inspector XE 2013. I am using 64 bit version  composer_xe_2011_sp1.7.256 to compile the code. The code shows error in line 104 of new_allocator.h.

Call stack for the error is

construct - new_allocator.h:104
push_back - stl_deque.h:1041

         I am trying to push a struct into a std::deque object. The struct is defined as follows

  struct something{

XML observations report only shows first instance of error

Hello,

I noticed inconsistency in observations report across formats - XML only shows the first stack while TXT shows all instances of any error. For example, there is an error P36 - showing 48 instances in observations.txt, but only shows one in observations.xml

Command-line:

"C:\Program Files (x86)\Intel\Inspector XE\bin32\inspxe-cl.exe" -report observations -report-all -format xml -report-output intelinspector_results\report_mi2_000_xml\intelinspector_observations.xml -result-dir intelinspector_results/mi2_000

windows 8.1 support?

In release notes for update 9, it says windows 8.1 support was begun with update 8.  

I submitted the full sources for my case in IPS 6000037395 which reports "waiting for customer" since over 3 weeks ago after I verified that the case works without internal error on win7 on an original core-i7 (running Intel64 mode in both cases).  The initial response, asking for the win7 comparison and sources, was prompt.

Was Windows 8.1 support withdrawn in update 9?

Inspector unable to detect memory leak

I have a function that allocates memory like :

void funcA(void* args)

{

   char* memory_leak = (char*)malloc(1000);

}

now I create a thread on this function, which therefore must allocate the mentioned memory, and exit.

My application is multi-threaded and I have created one more thread on this function.

But when I run Intel Inspector on my application, it doesnt show this as a memory leak.

I ran both mi1 and mi2 level of memory analysis but this leak was not detected.

Any ideas ?

 

Slow Level 2 analysis

Hi,

I have a graphics application and I want to run level 2 memory analysis on it.

But the application, because of the intel inspector, has become very very slow in response , so much so that it is impossible to play the game.

I have excluded all the modules that I do not want to instrument for analyses, but still the system is too slow(unplayable).

Can you suggest what more I can do to achieve more speed in terms of responsiveness of the game ?

 

 

Thanks.

 

Intel Inspector Optimization

Hi, 

I am trying to run the inspector on a game that uses about 200-300 MB of RAM. I run the inspxe-cl -collect ti1 . The inspector runs very slow on such a large application which I expected, but it seems that once my game and the inspector use up all my 2GB memory, the game becomes non responsive, that is it will either freeze or each click of the mouse will take 5 min to register. Once everything is so slow, it is impossible to interact with the game in order to cause possible deadlocks.

Unititialized memory access MPI_INIT Fortran MPICH

Hi,

when running inspxe with mi3 on my buggy mpi application (programmed in fortran, using MPICH 3.0.4 and ifort 12.0.5) it detects only an Unititialized memory access in my code in the line of

call MPI_INIT(ierr)

in module libc.so.6 and in source code line memcpy.S:194.

ierr was initialized before the call. Except of this initialization I do not have any other statement before MPI_INIT (only declarations). My application seems to have some memory currptions later in the program (but is at least executed on all nodes), where inspxe finds nothing.

 

Subscribe to Intel® Inspector XE