Re: Help needed on debugging a multithreaded application
In addition to Scott's not so wild guess, I'd suggest you install the
OS symbol files. Also, look at the list of loaded modules for the
process to find out which module that address resides in. You
need to check both the load address and the module size. Unless
this was a relocated executable, the crash must be in one of the
DLLs loaded into your process' address space. If you don't have
any DLL loaded that includes that address, this is either a thunk
(code injected into dynamically allocated memory) or invalid
callback address. At any rate, check your code whether you use
multimedia timers.
--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@mvps.org
MVP VC FAQ: http://vcfaq.mvps.org
=====================================
"Ronald RayGun" <insane@membrain.com> wrote in message
news:5I-dnS7mmvKX9hHanZ2dnUVZ8umdnZ2d@bt.com...
Ronald RayGun wrote:
I have written an application using VS2005. Although my application
itself does not create threads etc, I am using a third party DLL (which I
have the source code for), which creates and uses threads. My application
is using the same CRt as the third party DLL.
I have compiled my application to contain debug information in pdb files.
When I run my application, SOMETIMES it crashes unexpectedly. I have
tried debugging it by attaching the VS2005 debugger to the process -
however there is no stack trace available -
Correction - there is NO USEFUL (at least to me) information available.
Here is my stack trace:
027e123a()
winmm.dll!77577c89() [Frames below may be incorrect and/or missing, no
symbols loaded for winmm.dll] winmm.dll!77578f9d() winmm.dll!7757931d()
NTDLL.DLL!77f89c9d() KERNEL32.DLL!7c57b3bc()