Try changing the compiler's warning level. In maximum level it marks you as errors all the un-initialised variables.
On Apr 10, 2005 6:32 AM, NuclearFriend <[EMAIL PROTECTED]> wrote: > -- > [ Picked text/plain from multipart/alternative ] > Ben, I read somewhere that the debugger could do that, but it sounded a > little far fetched because I've seen uninitialised variables in a debugging > application. :( > > Is there any possible way to trace which variables aren't being initialised. > I have been going through my code and looking for any uninitialised > variables but this is very tedious. I have tried with memory breakpoints on > the first memory address given in the error but that doesn't seem to help > much. > > Pavol, this is happening with debug or release builds, it only depends on > whether or not the debugger is attached. > > Thanks for both your help so far. :) > > On Apr 10, 2005 4:38 AM, Pavol Marko <[EMAIL PROTECTED]> wrote: > > > > I have also experienced problems when doing weird stuff with memory > > (writing outside of allocated areas, etc.) a long time ago. MSVC's Debug > > build ran fine, Release crashed. I don't know how good Valve's memory > > manager is; I have used "mmgr" from Paul Nettle back then which worked > > fine for my purposes. > > > > Ben Everett schrieb: > > > > >Debug build in Visual Studio will assign default values to variables... > > >while in release build if you don't assign a default value in the > > >constructor or some initialization function you are just SOL. 90% of the > > >time assigning default values will fix this problem. > > > > > >-----Original Message----- > > >From: [EMAIL PROTECTED] > > >[mailto:[EMAIL PROTECTED] On Behalf Of NuclearFriend > > >Sent: Saturday, April 09, 2005 2:51 AM > > >To: [email protected] > > >Subject: [hlcoders] Crashing without debugger > > > > > >-- > > >[ Picked text/plain from multipart/alternative ] > > >Well I have made the mistake of not testing my builds regularly without > > the > > >debugger and now I am paying the price. Upon compiling a Release build > > and > > >giving it to my team, it now refuses to load a map when run without a > > >debugger. I get a "blah referenced memory at blah, memory could not be > > read" > > >error. > > > > > >Does anyone know where I can start to try and fix this problem? I've > > tried > > >to remove newer code but it seems to make no difference (so far, if I get > > no > > >help from here I'll just keep tearing stuff out until I find the > > problem).. > > >What are the major differences between running something with a debugger > > and > > >without one (I'd imagine nothing except that it would run slower)? > > > > > >PS The result is the same for debug or release builds. ;( > > >-- > > > > > >_______________________________________________ > > >To unsubscribe, edit your list preferences, or view the list archives, > > >please visit: > > >http://list.valvesoftware.com/mailman/listinfo/hlcoders > > > > > > > > >_______________________________________________ > > >To unsubscribe, edit your list preferences, or view the list archives, > > please visit: > > >http://list.valvesoftware.com/mailman/listinfo/hlcoders > > > > > > > > > > > > > > > > _______________________________________________ > > To unsubscribe, edit your list preferences, or view the list archives, > > please visit: > > http://list.valvesoftware.com/mailman/listinfo/hlcoders > > > > > -- > > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, please > visit: > http://list.valvesoftware.com/mailman/listinfo/hlcoders > > _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
