Re: Frame, View, Crash

Ajay Kalra wrote:


Ok,ok...
I kept pounding on it. I got it to crash doing something else by accedent!

Same call stack.

First-chance exception at 0x77c731fa in ars.exe: 0xC0000005: Access
violation reading location 0x00000008.

I have no idea where that is happening. Here is the first source I can
see on the stack.

BOOL AFXAPI AfxInternalPumpMessage()
{
....
    if (pState->m_msgCur.message != WM_KICKIDLE &&
!AfxPreTranslateMessage(&(pState->m_msgCur)))
    {
        ::TranslateMessage(&(pState->m_msgCur));
        ::DispatchMessage(&(pState->m_msgCur));
    }
   return TRUE;
}

The pointer is on 'return TRUE' so it must be in DespatchMessage. I was
in another frame/view than the CSummaryEditor. I sent a command that
changed the view configuration. Yet it must be something about the
CSummaryEditor. Here is the pState object:

- pState 0x00153bb8 {m_pModuleState=0x00000000 {m_pCurrentWinApp=???
m_hCurrentInstanceHandle=??? m_hCurrentResourceHandle=??? ...}
m_pPrevModuleState=0x00000000 {m_pCurrentWinApp=???
m_hCurrentInstanceHandle=??? m_hCurrentResourceHandle=??? ...}
m_pSafetyPoolBuffer=0x01238178 ...} _AFX_THREAD_STATE *

But it is only the message getting passed:
+ m_msgCur {msg=0x0000000f wp=0x00000000 lp=0x00000000} tagMSG

A WM_PAINT message.

I've got the degger sitting in this state, I'll leave it alone. Is there
any way to see where this message is going?

Thanks, Dan.