Re: [hlcoders] Crash in release mode only AND Changing the viewports
Well I was referring to gcc actually, since it's a much better and extremely helpful compiler when it comes to error-checking your code. But msvc has it too: configuration properties C/C++ General treat warnings as errors At 2006/04/30 11:15 PM, Nick wrote: >-- >[ Picked text/plain from multipart/alternative ] >which options? I tried to find those options in msvs2003 but i could not >find them > >On 4/30/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> >wrote: >> >> Well if you set the compiler options correctly, the code won't even >> compile when you access a variable without initializing it. Unfortunately >> Valve's SDK still needs a lot of work to be at that level. (I posted some >> of the changes on the KI list.) >> >> At 2006/04/27 03:57 AM, Garry Newman wrote: >> >-- >> >[ Picked text/plain from multipart/alternative ] >> >It always seemed backwards to me. >> > >> >When I'm in debug mode I want the compiler to do its best to try to make >> it >> >crash. I want it to throw a rain-man style spazz attack any time the >> >slightest thing is wrong. >> > >> >I dunno though, I've kind of heard the opposite too.. that the memory was >> >filled with random junk. >> > >> > >> > >> >On 4/27/06, Justin Krenz <[EMAIL PROTECTED]> wrote: >> >> >> >> What defines that all variables are initialized to 0? Is it a compiler >> >> flag, and why wouldn't you want this to be always set? This is the >> >> first I've heard of it. >> >> >> >> Ben Everett wrote: >> >> > The most common cause of crashes in release mode but not in debug are >> >> due to >> >> > variable initializations. In debug mode all variables are initialized >> to >> >> > '0', while in release mode they do not have a default initialization >> >> value. >> >> > >> >> > The most common cause of these crashes is failing to properly >> initialize >> >> > variables. >> >> > >> >> >> >> ___ >> >> 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
Re: [hlcoders] Crash in release mode only AND Changing the viewports
-- [ Picked text/plain from multipart/alternative ] which options? I tried to find those options in msvs2003 but i could not find them On 4/30/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Well if you set the compiler options correctly, the code won't even > compile when you access a variable without initializing it. Unfortunately > Valve's SDK still needs a lot of work to be at that level. (I posted some > of the changes on the KI list.) > > At 2006/04/27 03:57 AM, Garry Newman wrote: > >-- > >[ Picked text/plain from multipart/alternative ] > >It always seemed backwards to me. > > > >When I'm in debug mode I want the compiler to do its best to try to make > it > >crash. I want it to throw a rain-man style spazz attack any time the > >slightest thing is wrong. > > > >I dunno though, I've kind of heard the opposite too.. that the memory was > >filled with random junk. > > > > > > > >On 4/27/06, Justin Krenz <[EMAIL PROTECTED]> wrote: > >> > >> What defines that all variables are initialized to 0? Is it a compiler > >> flag, and why wouldn't you want this to be always set? This is the > >> first I've heard of it. > >> > >> Ben Everett wrote: > >> > The most common cause of crashes in release mode but not in debug are > >> due to > >> > variable initializations. In debug mode all variables are initialized > to > >> > '0', while in release mode they do not have a default initialization > >> value. > >> > > >> > The most common cause of these crashes is failing to properly > initialize > >> > variables. > >> > > >> > >> ___ > >> 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
Re: [hlcoders] Crash in release mode only AND Changing the viewports
Well if you set the compiler options correctly, the code won't even compile when you access a variable without initializing it. Unfortunately Valve's SDK still needs a lot of work to be at that level. (I posted some of the changes on the KI list.) At 2006/04/27 03:57 AM, Garry Newman wrote: >-- >[ Picked text/plain from multipart/alternative ] >It always seemed backwards to me. > >When I'm in debug mode I want the compiler to do its best to try to make it >crash. I want it to throw a rain-man style spazz attack any time the >slightest thing is wrong. > >I dunno though, I've kind of heard the opposite too.. that the memory was >filled with random junk. > > > >On 4/27/06, Justin Krenz <[EMAIL PROTECTED]> wrote: >> >> What defines that all variables are initialized to 0? Is it a compiler >> flag, and why wouldn't you want this to be always set? This is the >> first I've heard of it. >> >> Ben Everett wrote: >> > The most common cause of crashes in release mode but not in debug are >> due to >> > variable initializations. In debug mode all variables are initialized to >> > '0', while in release mode they do not have a default initialization >> value. >> > >> > The most common cause of these crashes is failing to properly initialize >> > variables. >> > >> >> ___ >> 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
RE: [hlcoders] Crash in release mode only AND Changing the viewports
I just did a simple test and got the behaviour I just explained.
#include
int main()
{
int *pValue;
printf("%p\n", pValue);
return 0;
}
VS.NET 7.1.3088 and VS8.0.50727.42
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jason Houston
Sent: Thursday, April 27, 2006 4:14 AM
To: hlcoders@list.valvesoftware.com
Subject: Re: [hlcoders] Crash in release mode only AND Changing the
viewports
--
[ Picked text/plain from multipart/alternative ]
I think MSVC tries to be a little too freindly sometimes :) My C lecturer
had a laugh when I said that the compiler initilises everything to 0 :D Oh
well, in most cases that's not a bad thing to have, but it would promote
some bad habits if you learnt using it.
--
Draco
--
___
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
Re: [hlcoders] Crash in release mode only AND Changing the viewports
-- [ Picked text/plain from multipart/alternative ] I think MSVC tries to be a little too freindly sometimes :) My C lecturer had a laugh when I said that the compiler initilises everything to 0 :D Oh well, in most cases that's not a bad thing to have, but it would promote some bad habits if you learnt using it. -- Draco -- ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
Re: [hlcoders] Crash in release mode only AND Changing the viewports
-- [ Picked text/plain from multipart/alternative ] It always seemed backwards to me. When I'm in debug mode I want the compiler to do its best to try to make it crash. I want it to throw a rain-man style spazz attack any time the slightest thing is wrong. I dunno though, I've kind of heard the opposite too.. that the memory was filled with random junk. On 4/27/06, Justin Krenz <[EMAIL PROTECTED]> wrote: > > What defines that all variables are initialized to 0? Is it a compiler > flag, and why wouldn't you want this to be always set? This is the > first I've heard of it. > > Ben Everett wrote: > > The most common cause of crashes in release mode but not in debug are > due to > > variable initializations. In debug mode all variables are initialized to > > '0', while in release mode they do not have a default initialization > value. > > > > The most common cause of these crashes is failing to properly initialize > > variables. > > > > ___ > 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
Re: [hlcoders] Crash in release mode only AND Changing the viewports
What defines that all variables are initialized to 0? Is it a compiler flag, and why wouldn't you want this to be always set? This is the first I've heard of it. Ben Everett wrote: The most common cause of crashes in release mode but not in debug are due to variable initializations. In debug mode all variables are initialized to '0', while in release mode they do not have a default initialization value. The most common cause of these crashes is failing to properly initialize variables. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
RE: [hlcoders] Crash in release mode only AND Changing the viewports
The most common cause of crashes in release mode but not in debug are due to variable initializations. In debug mode all variables are initialized to '0', while in release mode they do not have a default initialization value. The most common cause of these crashes is failing to properly initialize variables. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Fearn Sent: Wednesday, April 26, 2006 7:09 PM To: hlcoders@list.valvesoftware.com Subject: Re: [hlcoders] Crash in release mode only AND Changing the viewports On 4/26/06, ChromeAngel <[EMAIL PROTECTED]> wrote: > > > Subject: Re: [hlcoders] Crash in release mode only AND Changing the viewports > > scheme > > Reply-To: hlcoders@list.valvesoftware.com > > > > ChromeAngel wrote: > > > >> 2 Issues, I doubt they are related : > >> Issue 1) I've got my HL2DM mod running sweet and lovely and i'm about > >> ready to send it out to my testers, so I compiled in in release mode, > >> only to find it causes a crash in HL2.exe when I spawn on my listen > >> server. How should I go about finding the cause of this crash? > >> > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vccore98/ht ml/vcrefgz(catchrelease-builderrorsindebugbuild).asp > > > > -- > > Jorge "Vino" Rodrigue > > > Issue 1) Cheers for the URL Vino. By adding the /GZ parameter to my > debug compile I did manage to catch and fix a bug that was not otherwise > happening in debug builds. However, it still does not reproduce the > crash bug I get in release mode, even after full rebuilds. Any more > suggestions? Try this: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vccore/html /_core_turn_on_generation_of_debug_information_for_the_release_build.asp -- Jeff Fearn "Postmodernism: Once more without feeling." -- Geoffrey Nunberg ___ 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
Re: [hlcoders] Crash in release mode only AND Changing the viewports
On 4/26/06, ChromeAngel <[EMAIL PROTECTED]> wrote: > > > Subject: Re: [hlcoders] Crash in release mode only AND Changing the > > viewports > > scheme > > Reply-To: hlcoders@list.valvesoftware.com > > > > ChromeAngel wrote: > > > >> 2 Issues, I doubt they are related : > >> Issue 1) I've got my HL2DM mod running sweet and lovely and i'm about > >> ready to send it out to my testers, so I compiled in in release mode, > >> only to find it causes a crash in HL2.exe when I spawn on my listen > >> server. How should I go about finding the cause of this crash? > >> > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vccore98/html/vcrefgz(catchrelease-builderrorsindebugbuild).asp > > > > -- > > Jorge "Vino" Rodrigue > > > Issue 1) Cheers for the URL Vino. By adding the /GZ parameter to my > debug compile I did manage to catch and fix a bug that was not otherwise > happening in debug builds. However, it still does not reproduce the > crash bug I get in release mode, even after full rebuilds. Any more > suggestions? Try this: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vccore/html/_core_turn_on_generation_of_debug_information_for_the_release_build.asp -- Jeff Fearn "Postmodernism: Once more without feeling." -- Geoffrey Nunberg ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
Re: [hlcoders] Crash in release mode only AND Changing the viewports
Subject: Re: [hlcoders] Crash in release mode only AND Changing the viewports scheme Reply-To: hlcoders@list.valvesoftware.com ChromeAngel wrote: 2 Issues, I doubt they are related : Issue 1) I've got my HL2DM mod running sweet and lovely and i'm about ready to send it out to my testers, so I compiled in in release mode, only to find it causes a crash in HL2.exe when I spawn on my listen server. How should I go about finding the cause of this crash? http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vccore98/html/vcrefgz(catchrelease-builderrorsindebugbuild).asp -- Jorge "Vino" Rodrigue Issue 1) Cheers for the URL Vino. By adding the /GZ parameter to my debug compile I did manage to catch and fix a bug that was not otherwise happening in debug builds. However, it still does not reproduce the crash bug I get in release mode, even after full rebuilds. Any more suggestions? Issue 2) Prehaps someone else could explain how their team specific HUDs work? -ChromeAngel ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
Re: [hlcoders] Crash in release mode only AND Changing the viewports scheme
ChromeAngel wrote: 2 Issues, I doubt they are related : Issue 1) I've got my HL2DM mod running sweet and lovely and i'm about ready to send it out to my testers, so I compiled in in release mode, only to find it causes a crash in HL2.exe when I spawn on my listen server. How should I go about finding the cause of this crash? http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vccore98/html/vcrefgz(catchrelease-builderrorsindebugbuild).asp -- Jorge "Vino" Rodriguez ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
[hlcoders] Crash in release mode only AND Changing the viewports scheme
2 Issues, I doubt they are related : Issue 1) I've got my HL2DM mod running sweet and lovely and i'm about ready to send it out to my testers, so I compiled in in release mode, only to find it causes a crash in HL2.exe when I spawn on my listen server. How should I go about finding the cause of this crash? Issue 2) I'd like to change the Scheme the HUD is using to match the player's team. I've attempted to do this by loading team specific Schemes during the constructor of a HUD panel and monitoring for a change of team in the panel's OnThink (I would have preferred to use the player_team event, but I haven't found a good way to check if it matches the local player the first time it's called). When I detect the change of team i'm calling SetScheme on TeamFortressViewport, passing it the relevant scheme. Setting the scheme doesn't seem to be taking effect. Calling SetScheme with the scheme name, Repaint or ApplySchemeSettings to try and force the new scheme to be applied all cause crashes in vguii2.dll Your advice and assistance would be appreciated. -ChromeAngel ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
