[HELP] Used Debug mode / Error

Status
Not open for further replies.
Newbie Spellweaver
Joined
Apr 28, 2014
Messages
19
Reaction score
4
Bonjour, merci d'avance pour l'aide qui me sera apportée. :)
--:fanny:
Hello, thank you in advance for the help that will be brought to me. :)
Français :
Français d'origine alors j'utilise un traducteur désolé.Mon problème est lié au mode débogage, le WorldServer s'exécutant en mode débogage avec VS17 J'obtiens cette erreur:
Run-Time Check Failure #2 - Stack around the variable 'aEndRewardItem' was corrupted.Le programme '[9320] 7.WorldServer.exe' s'est arrêté avec le code 0 (0x0).
Screen :

ryuzakinara - [HELP] Used Debug mode / Error - RaGEZONE Forums
Pour finalement vous demander quelle serait la solution pour utiliser le mode Debug sans erreur ? :DOu si le débogage fonctionne quel erreur provoque le crash du WorldServer ?Screen 2 :
1 : 2 :
Merci !Demandez moi s'il vous manque des détail.
--English
French original then I use a sorry translator.My problem is related to the debug mode, the WorldServer running in debug mode with VS17 I get this error:
Run-Time Check Failure #2 - Stack around the variable 'aEndRewardItem' was corrupted.Le programme '[9320] 7.WorldServer.exe' s'est arrêté avec le code 0 (0x0).
Screen :

ryuzakinara - [HELP] Used Debug mode / Error - RaGEZONE Forums
To finally ask you what would be the solution for using Debug mode without error ? :DOr if the Debug works which error causes the WorldServer crash ?Screen 2 :
1 : 2 :
Thank you !Ask me if you miss details.
 
Hey,

Stack = Type of memory.

This typically happens with a buffer overflow.

Things to always check are:
Array (denoted by [num] or *) Lengths (szLinkChar in your chase) -> Increase size, find the largest size it's trying to read in and add a few extra for safety.
Possible overrites by others arrays, another array maybe writing into the storage location of another. Step through the code in VS using F10 and this should tell you where the exception is happening.

Lastly if you are in debug mode and you notice an exception (error) you should always resolve, because if in release mode it "works" it will still be there and will cause you problems along the line, and at this point it will typically be much harder to resolve (database data correction is a *****)
 
Upvote 0
Status
Not open for further replies.
Back