Tracing Fatal Application Error

Tracing Fatal Application Error

• Zero_

  Ok, thanks for your answer, i'm trying to find if i used not initialized value in my code. Do you think that is the reason of a moving bug. Because my bug not appears at the same moment if I'm in debug or release. The bug appears sooner in release than in debug.
  
  I can't use the debug mode because my C++ process are call by a C# process.
  
  This type of bug can appears without not initialized value problem
  
  Thanks.
  
  
  
  
  
  

• MrJP

  It is a very likely reason for such bug. And yes, you can debug C++ code invoked from C# application. If you are using VS2005 see

  http://msdn.microsoft.com/library/default.asp url=/library/en-us/dnppcgen/html/device_debug_vs2005.asp

  For VS2003 + eVC4 see http://www.alexfeinman.com/articles/PInvoke-Debugging/PIDebug.htm

  
  
  

• StarRrr

  This error (access violation) is most frequently caused by a unitialized value. E.g. if you have

  int i;

  int arrValues[10];

  ...

  int z = arrValues;

  and you never set the value of i, in Debug mode it will be initialized to 0xCDCDCDCD and naturally cause an access violation when used as an array index. In release mode it willl be 0 and not cause any errors, but produce a wrong result.

  To catch this, run the application under debugger and in the Debug/Exceptions open Win32 Exceptions and check the box against c0000005, then run the application and see the stack when it breaks

  
  
  

• Rajesh Kumar J

  I continue to receive a rasautou.exe--Application error The insturction at 0x7c911ec3 referenced memory at 0x000dd05a. The memory could not be written. Continues to pop up I am not so computer savvy. Thank You
  
  

• StealthyC

  Ok, thanks for your answers, my error would be a not initialized value.
  
• Tracing Fatal Application Error