🔒 Locked

Is Release mode different from Debug?

Started by Roof Top Pew Wee Dec 7, 2001 at 4:36 PM 3 replies 200+ views

Original Post

Dec 7, 2001 at 4:36 PM

I have just finished a windowed program in DX, but when I build it in release mode, rather than debug, it runs, but some of my things don''t work or appear. I have a GUI written, and in debug mode, it all works fine. The buttons show up and when the y are clicked on, they do their appropriate functions and so on. But when I compile and run the program in Release, the buttons don''t show up. I checked the links for the DX .lib files, and that all works fine, and I don''t think that that is the problem because I still get the program to compile. I looked in my Windows programming book, but it didn''t have much information on how to do release versions of programs. Does anyone know of some basic rules to follow when making release version of a program (common things to watch out for) or if my question is one that is too difficult to answer from what I have said, does anyone know of any tutorials? If anyone is diligent enough, I can send my code. I''m sorry, but I''ve run out of places to look, so I thought this might work. Thanks in advance to anyone that answers. --Vic--

Floppy

Dec 7, 2001 at 4:44 PM

Main differences between debug and release:

Debug keeps information for use of debugging

By doing this the debug code is larger than it should be (quite a bit usually)

Release mode gets rid of the debug information

By doing this the release code is a LOT smaller than the debug code (dependent upon length of code)

The compiler generates more optimized code

There others, but that''s the basics. I found this really good site that explains everything I could have explained to you. Here it is:
Go Here

Hope you get your problem solved!

Null and Void

Dec 7, 2001 at 4:48 PM

quote:
Original post by Floppy
The compiler generates more optimized code [in release mode]

Debug mode wipes pointers when they''re not used, initilializes them on creation, and other such safety features (lots with pointers). Are you sure you''re initializing everything correctly?

[Resist Windows XP''s Invasive Production Activation Technology!]

Roof Top Pew Wee

Dec 7, 2001 at 5:20 PM

I''d imagine that I''m using my pointers correctly, but I may not be. Give me an example of what you mean by incorrect pointer usage. It seems to me that a release verions would just "fix" any incorrect usage like forgetting to initialize pointers.

--Vic--

a person

Dec 7, 2001 at 8:48 PM

release version does optimization and is meant to ensure quick code excution AFTER you fix you bugs. all safty nets are dropped. improper pointer usage include: going out of the allocated memory with a too high index, using a pointer that has not been given a value that points to valid memory owned by yoru program, not freeing a pointer you malloced of not deleting a pointer you newed. use varibles without giving them values (since they are undefined NOT zero).

Topic Locked

This topic has been locked by a moderator. New replies are not allowed.