Release vs. Debug in WTL
-
Hi. The application I coded is ATL/WTL windows app, now everything is fine in debug, when I compile it in release it compiles with no errors, however strings for label and other controls are cut off, it shows like only the first letter or nothing. I get the strings from string table in the local resource, and it works fine in debug mode, I also checked the encoding and it is MBCS defined in both release and debug versions. What can cause this behavior? Thanks.
Sarajevo, Bosnia
-
Hi. The application I coded is ATL/WTL windows app, now everything is fine in debug, when I compile it in release it compiles with no errors, however strings for label and other controls are cut off, it shows like only the first letter or nothing. I get the strings from string table in the local resource, and it works fine in debug mode, I also checked the encoding and it is MBCS defined in both release and debug versions. What can cause this behavior? Thanks.
Sarajevo, Bosnia
Check if you have missed any setting. Have a look at difference betn debug and release[^] for possible cause. Though this article may not be very useful in this context, but may be you get some idea.
Prasad Notifier using ATL | Operator new[],delete[][^]
-
Check if you have missed any setting. Have a look at difference betn debug and release[^] for possible cause. Though this article may not be very useful in this context, but may be you get some idea.
Prasad Notifier using ATL | Operator new[],delete[][^]
-
Hi. The application I coded is ATL/WTL windows app, now everything is fine in debug, when I compile it in release it compiles with no errors, however strings for label and other controls are cut off, it shows like only the first letter or nothing. I get the strings from string table in the local resource, and it works fine in debug mode, I also checked the encoding and it is MBCS defined in both release and debug versions. What can cause this behavior? Thanks.
Sarajevo, Bosnia
It's likely that you've not initialised a variable - when I've had Release/Debug issues, that's what it's usually been. I always make sure that I include Debug information in Release builds - that way I can use the debugger with Release builds reasonably meaningfully - as long as you keep optimisations turned on and you use the Release version of the C run-time, you've still got a Release build.
-
It's likely that you've not initialised a variable - when I've had Release/Debug issues, that's what it's usually been. I always make sure that I include Debug information in Release builds - that way I can use the debugger with Release builds reasonably meaningfully - as long as you keep optimisations turned on and you use the Release version of the C run-time, you've still got a Release build.
-
Thanks, I'll give it a try. I am not sure about having debug info in the release build, but I will use it at least for the sake of finding out what the problem is. Thank you.
Sarajevo, Bosnia
Some more info - the debug info will be held separately (in a PDB file), so there is a) no symbol information exposed in the EXE, and b) little change in size in the EXE.