find crash location in the code
-
Windows 7, Visual Studio 2010, C++ An application I wrote that has been running for over a year has just started getting an unhandled exception. It is _com_error and the exact return value if E_FAIL, an unspecified error. That is unhelpful. The crash window specifies an address where the crash occurred. Question: How does one take that address and find the place in the code where the program was executing when the exception was first thrown?
Thank you for your time If you work with telemetry, please check this bulletin board: www.irigbb.com
-
Windows 7, Visual Studio 2010, C++ An application I wrote that has been running for over a year has just started getting an unhandled exception. It is _com_error and the exact return value if E_FAIL, an unspecified error. That is unhelpful. The crash window specifies an address where the crash occurred. Question: How does one take that address and find the place in the code where the program was executing when the exception was first thrown?
Thank you for your time If you work with telemetry, please check this bulletin board: www.irigbb.com
This is an old article, but I believe it still applies: Post-Mortem Debugging Your Application with Minidumps and Visual Studio .NET[^]
The difficult we do right away... ...the impossible takes slightly longer.
-
Windows 7, Visual Studio 2010, C++ An application I wrote that has been running for over a year has just started getting an unhandled exception. It is _com_error and the exact return value if E_FAIL, an unspecified error. That is unhelpful. The crash window specifies an address where the crash occurred. Question: How does one take that address and find the place in the code where the program was executing when the exception was first thrown?
Thank you for your time If you work with telemetry, please check this bulletin board: www.irigbb.com
Here's another much more recent article about what you can do to find the error: Investigate crashes: c stack trace and dumps[^]
The difficult we do right away... ...the impossible takes slightly longer.
