User Guide


Unhandled Application Exception

Occurs when an unhandled exception is detected that causes the application program to crash.
Problem type: Dangling lock
Code Location
Represents the instruction that threw the exception.
void problem1(int *y) { *y = 5; } void problem2() { int x = new int; }
In these (simplified) example functions, two exceptions are possible:
  • Variable
    may not reference a valid memory location and therefore the write may cause an exception to be thrown. If that exception is not properly handled, the Dependencies Report will show an
    Unhandled application exception
    pointing to the write of
  • If the process is out of memory, the allocation will throw an exception. If the exception is not handled, the Dependencies Report will show an
    Unhandled application exception
    associated with the allocation.
Because of the abnormal process termination (crash), the Dependencies tool may also report a
Missing end task
Missing end site
Possible Correction Strategies
This problem usually exposes an existing bug in your application that appears when the application is run with the Dependencies tool.

Product and Performance Information


Intel's compilers may or may not optimize to the same degree for non-Intel microprocessors for optimizations that are not unique to Intel microprocessors. These optimizations include SSE2, SSE3, and SSSE3 instruction sets and other optimizations. Intel does not guarantee the availability, functionality, or effectiveness of any optimization on microprocessors not manufactured by Intel. Microprocessor-dependent optimizations in this product are intended for use with Intel microprocessors. Certain optimizations not specific to Intel microarchitecture are reserved for Intel microprocessors. Please refer to the applicable product User and Reference Guides for more information regarding the specific instruction sets covered by this notice.

Notice revision #20110804