Project Runtime Library Option
-
Hi everyone, I'm working on an IE toolbar.Everything went fine until i had to add a dialog box of some kind of user setting.Dialog opens,does its work and closes just fine on my development computer,but on other computers it does not.The button which is supposed to open the dialog does nothing.After some try-and-error experience,I found out that the problem was Runtime Library setting under Code Generation section of the project properties dialog. Whenever i select a Non-Debug runtime library,the dll built does not work on other systems.When I select a Debug runtime library (like Multi-threaded Debug (/MTD) or Multi-threaded Debug DLL (/MDd)) it builds and works out fine.But it also doubles the dll file size and much likely with debug information which is unnecessary in the release build. Has anyone any idea what the case might be?
-
Hi everyone, I'm working on an IE toolbar.Everything went fine until i had to add a dialog box of some kind of user setting.Dialog opens,does its work and closes just fine on my development computer,but on other computers it does not.The button which is supposed to open the dialog does nothing.After some try-and-error experience,I found out that the problem was Runtime Library setting under Code Generation section of the project properties dialog. Whenever i select a Non-Debug runtime library,the dll built does not work on other systems.When I select a Debug runtime library (like Multi-threaded Debug (/MTD) or Multi-threaded Debug DLL (/MDd)) it builds and works out fine.But it also doubles the dll file size and much likely with debug information which is unnecessary in the release build. Has anyone any idea what the case might be?
I always use the multithreaded CRT, which is staticly linked into the DLL. That way it will (or should) work on any machine regardless of what CRT DLLs are installed.
--Mike-- Visual C++ MVP :cool: LINKS~! Ericahist | PimpFish | CP SearchBar v3.0 | C++ Forum FAQ
-
I always use the multithreaded CRT, which is staticly linked into the DLL. That way it will (or should) work on any machine regardless of what CRT DLLs are installed.
--Mike-- Visual C++ MVP :cool: LINKS~! Ericahist | PimpFish | CP SearchBar v3.0 | C++ Forum FAQ
Thanks for the response, I digged up the code a little bit further and found out the problem was an uninitialized HWND value. something like; HWND hwndWB2; // the "guilt" m_spWebBrowser2->get_HWND((SHANDLE_PTR *)&hwndWB2)); ... ... MyDialog dialog = MyDialog(); dialog.DoModal(hwndWB2); When the guilt line is modified as: HWND hwndWB2 = NULL; everything's OK. but the reason why it works with Debug CRT is still a curiosity.
-
Thanks for the response, I digged up the code a little bit further and found out the problem was an uninitialized HWND value. something like; HWND hwndWB2; // the "guilt" m_spWebBrowser2->get_HWND((SHANDLE_PTR *)&hwndWB2)); ... ... MyDialog dialog = MyDialog(); dialog.DoModal(hwndWB2); When the guilt line is modified as: HWND hwndWB2 = NULL; everything's OK. but the reason why it works with Debug CRT is still a curiosity.
It's probably more that it's compiled with run-time checks on (/RTC1 flag) - the compiler can put in extra code when compiling to help find problems like overwriting bits of the stack or heap you shouldn't do. This requires stack/heap to be initialised to known values, which it does (it actually sets them to 0xcccccccc). These values are probably recognisable as invalid by DoModal (or IsWindow, or something), so it just rejects them. In Release, the HWND isn't initialised at all, so may contain a value that *could* be a valid HWND, causing the crash?