How Can I Debug Access Violations When Running My Program Outside the Debugger?
This topic applies to:
Edition |
Visual Basic |
C# |
C++ |
Web Developer |
|---|---|---|---|---|
Express |
.gif "Topic does not apply") |
|
Native only |
|
Standard |
|
|
Native only |
|
Pro and Team |
|
|
Native only |
|
Table legend:
.gif "Topic applies") |
Applies |
|
Does not apply |
.gif "Topic applies but command hidden by default") |
Command or commands hidden by default. |
Problem Description
My program runs fine in the Visual Studio environment, but when I run it stand alone with the Windows operating system, it produces an access violation. How can I debug this problem?
Solution
Set the Just-in-time debugging option and run your program standalone until the access violation occurs. Then, in the Access Violation dialog box, you can click Cancel to start the debugger.
Also see the Knowledge Base article Q133174, "How to Locate Where a General Protection (GP) Fault Occurs." You can find Knowledge Base articles on the MSDN Library CD or at http://search.support.microsoft.com.