persistent crash on tester's computers that I can't reproduce
-
Snakefoot wrote:
A proper container is one that keeps track of its allocation like std::vector or MFC::CSimpleArray. But I see that you are using CRecentFileList(), and it seems to be without such features.
I put in a check that the list exists, and for some reason I cannot fathom, it is not created properly on this one guy's system, though it works fine for everyone else. I can't imagine what he can be doing on his computer that would prevent this standard MFC call from working properly. Does anyone know? I'd rather not do it all manually if I don't have to. I'd rather detect systems that don't support it, but I don't know of any reason why a system would not support it. Can anyone make a guess on this?
I fixed the problem. I still have no idea why the standard call wasn't working on his system. But I changed this:
LoadStdProfileSettings(4);
to
CString strSection = "Recent File List"; CString strEntryFormat = "File%d"; m\_pRecentFileList = new CRecentFileList(1, strSection, strEntryFormat, 4); m\_pRecentFileList->ReadList();
And voila! No crashes - it's working fine. I can't believe I spent a week and a half of my life on this. On the plus side, my startup code is vastly cleaner after 10 days of intense scrutiny.