1. CSplitterWnd crashes in release build after 2005 upgrade
Hi, I have run into a problem that has me stopped dead! I have an existing (and working!) VS 6 application which I have recently upgraded to VS 2005. The application works without problems when run built for debug, but crashes below the CreateView() method of CSplitterWnd when built for release. By turning on the debug switch with the "release" build (but keeping the release libraries), I was able to get a traceback which indicates that the access violation occurred in ntdll.dll. The call stack looks like: ntdll.dll!7c9012b4() ... kernel32.dll!7c80e2c5() kernel32.dll!7c80b53c() rms.exe!CDllIsolationWrapperBase::GetModuleHandleA() line198 rms.exe!CComCtlWrapper::GetProcAddress_InitCommonControlsEx() line 241 rms.exe!AfxEndDeferRegisterClass() line 4497 rms.exe!CFormView::Create() line 90 rms.exe!CSplitterWnd::CreateView() line291 rms.exe!CMainFrame::OnCreateClient() line 296 ... The RuntimeClass being instantiated in the CreateView() call is apparently valid (its data looks good in the debugger). The crash happens right at startup during the CMainFrame::OnCreateClient() call, so the app really hasn't had much opportunity to corrupt memory yet - it has only executed "boiler-plate" code so far (besides - it works correctly in debug mode with or without the debugging heap turned on). The application uses the multi-threaded, static-linked version of MFC. The problem only occurs when built in VS 2005. No problems in VS 6! Any suggestions are welcome! Thanks, --- leon gordon