Zyrenthian
Programmer
Hi All,
I just wanted some insight into a bug I have. "Sometimes", when running our app in the debugger, an exception occurs in shcv.dll (dll used by mfc debugger to handle debug symbols). I am lead to believe that it is a thread issue. I say this because if I set a break point and step through to find the exception, it does not happen. My question to you is this:
Our original code called "PostMessage(WM_CLOSE)" when we clicked on the exit button. PostMessage will post the message and return imediately as opposed to "SendMessage(WM_CLOSE)" which will wait for the call to complete before returning. My assumption is that our application continues on with the closing procedure while PostMessage is or is about to be processed. When our app closes before all the other messages are processed, an exception occurs in the shcv.dll. Maybe the handle was released and we are accessing invalid memory?
What are your thoughts on my theory or has anyone ever seen this problem?
Matt
Using: VC++ 6.0 sp5
Symptom of problem (WHICH REALLY STINKS): When this exception does occur, it unloads my project from the workspace and loads up msdev.exe in its place. Every time I test the bug, I have to reload my project if it is reproduced. *MY PROJECT TAKES ABOUT 10 MINUTES TO RELOAD*
I just wanted some insight into a bug I have. "Sometimes", when running our app in the debugger, an exception occurs in shcv.dll (dll used by mfc debugger to handle debug symbols). I am lead to believe that it is a thread issue. I say this because if I set a break point and step through to find the exception, it does not happen. My question to you is this:
Our original code called "PostMessage(WM_CLOSE)" when we clicked on the exit button. PostMessage will post the message and return imediately as opposed to "SendMessage(WM_CLOSE)" which will wait for the call to complete before returning. My assumption is that our application continues on with the closing procedure while PostMessage is or is about to be processed. When our app closes before all the other messages are processed, an exception occurs in the shcv.dll. Maybe the handle was released and we are accessing invalid memory?
What are your thoughts on my theory or has anyone ever seen this problem?
Matt
Using: VC++ 6.0 sp5
Symptom of problem (WHICH REALLY STINKS): When this exception does occur, it unloads my project from the workspace and loads up msdev.exe in its place. Every time I test the bug, I have to reload my project if it is reproduced. *MY PROJECT TAKES ABOUT 10 MINUTES TO RELOAD*