It *does* make it to the CMainFrame constructor. I had put a breakpoint
within the body and it never made it there. I put a breakpoint on the
"open" paren for the function and it stopped. I am now stepping through to
It does not reach the CMainFrame constructor. I can step into the malloc
in afxmem that returns the pointer 0x00ae0068, and back out to the
original break point on the line shown below (in InitInstance() ):
CMainFrame* pFrame = new CMainFrame;
As soon as I step off of this line the program closes.
Thanks,
Tom
"AliR (VC++ MVP)" <A...@online.nospam> wrote in message
news:ZlXBj.17348$Ch6.8224@newssvr11.news.prodigy.net...
Did you check you CMainFrame constructor? Set a break point there to see
if it reaches that code, and if there is an error there.
AliR.
"Tom Salicos" <TSali...@Drykilns.net> wrote in message
news:O7zGDEHhIHA.4376@TK2MSFTNGP05.phx.gbl...
I have an AppWizard-created MFC program that will not run on my
development computer any longer. This just happened. It *will* run on
other computers. Older versions of the same program which I know I
debugged on my development computer will now not run. All other
dialog-based and MDI programs run okay. This one just closes immediately
and there are no error messages other than the memory leaks that I would
expect.
This is VC++ 6.0.
The problem happens in Debug or Release mode.
In Debug the program closes immediately after this line:
CMainFrame* pFrame = new CMainFrame;
If I debug into the module AFXMEM.CPP I get this:
void* PASCAL
CObject::operator new(size_t nSize, LPCSTR lpszFileName, int nLine)
{
return ::operator new(nSize, _CLIENT_BLOCK, lpszFileName, nLine);
}
nSize == 60836, lpszFileName is the path to MyApp.CPP and nLine is 126.
The return is 0x00ae0068.
Is there enough info here to deduce anything?
Doesn't it seem like something is corrupted on my development computer?
Thanks for help,
Tom S