Some morequestions, that may clarify the issue:
Are you using a batch-file to call your application?
Does the application use dlls or it's statically linked with libs?
What is the memory footprint of your application?
How long does your workload run?
Does your application end normally or by using a terminate function?
Does your application fork?
Thanks for the details.
There might be a problem with statically linked executable. I can't say for sure right now, but as far as I remember Call Graph doesn't work properly with statically linked binaries on Windows, but I need to check it.
I forgot to give you a nice link to the page with the steps of how to resolve CG issues. Please, try it as well.
Besides, I'd like to look at the CG project results. Would you please find the results directory (usually it's under
From the logs it revealed that an anti-virus program "Sophos Anti-Virus" dynamically injects DLL D:ProgrammeSophosSophos Anti-Virussophos_detoured.dll into instrumented process.
It apparently conflicts with dynamic instrumentation engine.
Please, try to temporary stop this anti-virus service and then re-run the analysis. In case of failure, please attach the results directory as well.
Sorry for the delay, I was on vacation and it took some time to communication with engineers who looked at the logs.
Unfortunately, from the attached logs they did not find anything suspected besides the original concern wrt. Sophos. Binary sophos_detoured.dll from this product is still injected into profiled process. According to what is mentioned on Sophos support site, the DLLs from the list are loaded (injected) into any created process at early stage. The problem that some will try to instrument certain system APIs and thus will conflict with VTune CG instrumentation engine (Bistro) run-time that will try to do the same thing, probably with the same APIs. It will certainly lead to fast process crash as coexistence of multiple similar instrumentation engines in the same process is not supported.
Sophos_detoured.dll is most probably uses binary instrumentation, since, as mentioned in its name, it uses detour, Microsoft's engine for instrumentation of system APIs.
Just to check this, please, try to profile your application on another machine where Sophos was never installed.
Just another hint: try to temporary remove any DLLs from registry key HKLMSoftwareMicrosoftWindows NTCurrent VersionWindowsAppInit_Dlls, reboot, create new VTune call graph project for the app of interest and profile.