Re: How to step into MFC code.
"ultranet" wrote:
Yes, i was doing just that. Maybe it didn't work because it was
ReleaseWithDebug build. I'll try TestRelease or Debug builds, if they build
for me.
Well, in Debug build i was able to step into MFC, but i've noticed just as
many times before, Debug builds crash in weird places. This time, i got a
crash in:
LRESULT CALLBACK
AfxWndProc(HWND hWnd, UINT nMsg, WPARAM wParam, LPARAM lParam)
{
// special message which identifies the window as using AfxWndProc
if (nMsg == WM_QUERYAFXWNDPROC)
return 1;
// all other messages route through message map
CWnd* pWnd = CWnd::FromHandlePermanent(hWnd);
ASSERT(pWnd != NULL); // this failed
ASSERT(pWnd->m_hWnd == hWnd); // here
return AfxCallWndProc(pWnd, hWnd, nMsg, wParam, lParam);
}
In another project, just linking to our i18n lib, even if we don't call into
it in any way, was causing a crash in Debug build, w/ some threading issues.
Is this because some of the code is Release, and some Debug, and they use
different heaps, or something to that effect, and step on each other's toes?
Since i can't build everything in debug (there are too many dependencies
some of which don't even build in Debug), i'm afraid i have to go back to
ReleaseWithDebug.