Do-it-yourself MFC DLL
-
Should you be able to create your own mfc42.dll from the MFC/SRC source files (plus whatever else is available to the VC++ developer)? I'd like to put some breakpoints in MFC code to debug a release-only problem. dahill
No, you can't. Your release only problem is probably a problem with memory that you're not initialising properly, debug mode does it for you. The best way to check that stuff is to write logging code in your exe and read the log after running it. Christian Graus - Microsoft MVP - C++
-
Should you be able to create your own mfc42.dll from the MFC/SRC source files (plus whatever else is available to the VC++ developer)? I'd like to put some breakpoints in MFC code to debug a release-only problem. dahill
A release-only problem screams uninitialized variable, or a pointer problem. I use TRACE statements. ------- sig starts "I've heard some drivers saying, 'We're going too fast here...'. If you're not here to race, go the hell home - don't come here and grumble about going too fast. Why don't you tie a kerosene rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt "...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
