Re: Tracing a memory access error without using the debugger.
"TomChapman" <TomChapman12@gmail.com> wrote in message
news:#cFeEBe9KHA.3176@TK2MSFTNGP05.phx.gbl...
My program occasionally terminates with a memory access violation. The
description is shown below:
The thread tried to read from or write to a virtual address for which it
does not have the appropriate access. Error code: 0xC0000005 Exception
address: 0x0047AC19.
Finding this problem would be easy if I was running the debugger.
Unfortunately, on the server where this occurs, I can not load the
compiler and run the debugger. The error doesn't occur when the program is
run elsewhere. Does the exception address included in the error mean
something useful? Is there a way for me isolate where in my code the error
is occurring?
This is a release version of software. I could install the debug version
if that would help. This is Visual C++ version 6. What can I do here?
Install a debug version complete with the .pdb files. Run the program until
it crashes. Fire up Process Explorer from Sysinternals.com. In the process
list, find the crashed process, right click, choose Properties. Look at the
Threads tab. You can see the call stack of each thread by clicking the
Stack button. The call stack will have function names because of the .pdb
files that are present. It's not the same as having a full debugger because
you can't see variable values, but at least you can see a symbolic stack
frame, and this is really easy to deploy (no installing Remote Debugger,
establish network connection, set security permissions, etc.).
-- David