Debugging Native Code FAQs

Note

This article applies to Visual Studio 2015. If you're looking for the latest Visual Studio documentation, see Visual Studio documentation. We recommend upgrading to the latest version of Visual Studio. Download it here

The following topics contain answers to some frequently asked questions:

• How Can I Debug Access Violations When Running My Program Standalone?

• How Can I Debug an Access Violation?

• How Can I Find Out If My Pointers are Corrupting a Memory Address?

• How Can I Find Out Who Is Passing a Wrong Parameter Value?

• When Calling a Function Hundreds of Times, Which Call Failed?

• Where Can I Look Up Win32 Error Codes?

• How Can I Keep Focus When Stepping Through My Program?

• How Can I Use Debugger Windows While Debugging a Foreground Program?

• If Halted in MFC, How Can I Get Back to the Function That Called MFC?

See Also

Debugger Security
Debugging Native Code