Visible to Intel only — GUID: GUID-004433E5-7AFB-4D22-B351-A41314FD5438
Visible to Intel only — GUID: GUID-004433E5-7AFB-4D22-B351-A41314FD5438
Troubleshooting Application Crashes
Symptoms
The application crashes when you run an Intel Inspector analysis.
Details
Both the application and the Intel Inspector run in the same address space. This means:
A bug that can cause the application to crash while running without the Intel Inspector can cause the application to crash while running with the Intel Inspector.
A bug that does not manifest itself and does not cause the application to crash while running without the Intel Inspector may manifest itself and cause the application to crash while running with the Intel Inspector because of parallel non-deterministic scheduling or techniques used to detect incorrect memory accesses.
Possible Correction Strategies
Use a conventional debugger to debug the crash.
Run a memory error analysis to help debug memory-related crashes before running a threading error analysis.
If the application crashes during analysis and the Intel Inspector reports errors before the application crashes, interpret the result data to determine if any of the reported errors caused the crash. A likely culprit should be near the bottom of the Collection Log pane.
Contact the Intel Customer Support team by email. Include a description of the steps leading up to the problem, the generated problem report, and the corresponding result directory.