Client crash...unknow problem o.o

ogeid · Post by **ogeid** » Fri Jan 26, 2007 1:24 am

see ss plz

when i put 1 string in New Char name box i got crash

i make a lot of changes in my client ...but i never modified updatenewchar function in my client...

bone-you · Post by **bone-you** » Fri Jan 26, 2007 2:01 am

See all that overlay text on the bottom left? That's your problem

ogeid · Post by **ogeid** » Fri Jan 26, 2007 2:16 am

that overlay text is from createscreenshoot function i eraesed that and i still bugged

bone-you · Post by **bone-you** » Fri Jan 26, 2007 2:19 am

ogeid wrote: that overlay text is from createscreenshoot function i eraesed that and i still bugged

*WOOSH* over your head.

The *text* has nothing to do with it. It's what the text says. All I can say is go back to the original copy and -START OVER-.. unless you have the patience and time to figure it out yourself. Never seen this problem before.

ogeid · Post by **ogeid** » Fri Jan 26, 2007 2:45 am

bone-you wrote:
ogeid wrote: that overlay text is from createscreenshoot function i eraesed that and i still bugged
*WOOSH* over your head.

The *text* has nothing to do with it. It's what the text says. All I can say is go back to the original copy and -START OVER-.. unless you have the patience and time to figure it out yourself. Never seen this problem before.

Drazz · Post by **Drazz** » Fri Jan 26, 2007 10:40 am

Run your app from MSVC++ IDE in Debug mode and then check the error line (run it with window mode activated)

ogeid · Post by **ogeid** » Fri Jan 26, 2007 5:01 pm

thanks but i dont know what this means

bone-you · Post by **bone-you** » Fri Jan 26, 2007 5:28 pm

ogeid wrote:

thanks but i dont know what this means

It's called ASM and he meant look at the SOURCE for the problem. If you didn't know THAT you shouldn't be trying to compile/customize sources for your server.

Sentinel · Post by **Sentinel** » Fri Jan 26, 2007 9:13 pm

Oh come on Zero. Bash him again!

bone-you · Post by **bone-you** » Fri Jan 26, 2007 9:14 pm

Sentinel wrote: Oh come on Zero. Bash him again!

You just had to comment didn't you. Aren't you dead yet? If not, why not?

Sentinel · Post by **Sentinel** » Fri Jan 26, 2007 9:18 pm

Oh c'mon. It's for shits n giggles man. Rofl... It's fun not having people bitch at me 24/7. >.>

tester · Post by **tester** » Fri Jan 26, 2007 9:47 pm

bone-you wrote:
ogeid wrote:

thanks but i dont know what this means
It's called ASM and he meant look at the SOURCE for the problem. If you didn't know THAT you shouldn't be trying to compile/customize sources for your server.

try running command line, type cmd, then type debug, then type a, and ur in assembler mode xD

in debug u can check ur registers and shit, and check if their values are right.

Hope this helped a bit
And bone and sent, PLEASE! Dont be hating ! xD
just had to quote that from a movie i saw yesterday xD

Cheers Tester

bone-you · Post by **bone-you** » Fri Jan 26, 2007 10:27 pm

The guy doesn't know what ASM is or what that screen is. He needs to be in debug mode through the source and not the JIT debugger which is probably what he did.

xenx · Post by **xenx** » Sat Jan 27, 2007 2:01 am

ey bone, wanna give a quick shot at explaining how to get into debug mode for the source?

whenever i try to debug anything i get what this guy has.. and i also dont have a clue wtf it is, well no i know what its called now you just said hehe.. but i wouldnt mind being able to debug stuff properly...

edit.. actually iv just rememberd where the debug part is for where your in sources, but whenever iv ever tried to do it, lets say for the HGserver, when it runs the HG it cant find any of the associated files ie: u get item configuration error etc in the HG because it cant find any of the item.cfg's, i did the obvious and put all the configs in the debug folder, where the compiled .exe goes.. but still gives the same problem..

bone-you · Post by **bone-you** » Sat Jan 27, 2007 2:20 am

The reddish circles are the debug controls inside VS.

You load up the sources (solution/project/workspace depending on what VS version you have, or something similar if you use another application), you click the green arrow button (or the debug menu->Start Debugging) and when it comes across an error it will temporarily halt the client and bring you to the sources and show you the problem.

Oh I forgot to mark the breakpoints. That yellow arrow with a reddish circle around it. If you click that area next to code it will set a breakpoint at which point it will cut the processing and bring you to that code when it comes across it. The yellow arrow is the current place in the code that it's at.

Breakpoints are a very important thing in debugging. If you get an error somewhere and can't figure out why, you can set breakpoints before it and step into it (F11/F10).

If you don't have the debug toolbar I have, right click somewhere on the toolbar area and add Debug and Debug Location. Two very important toolbars