+- SphereCommunity (https://forum.spherecommunity.net)
+-- Forum: Sphere 0.56d (/Forum-Sphere-0-56d)
+--- Forum: General Help (/Forum-General-Help)
+--- Thread: How can i find out the reason of this debug? (/Thread-How-can-i-find-out-the-reason-of-this-debug)
How can i find out the reason of this debug? - Blueberryyy - 06-11-2017 09:10 AM
02:06:DEBUG:__ thread (2888) __ | # | _____ function _____________ | ticks passed from previous function start ______
02:06:DEBUG:>> 2888 | 0 | NetworkManager::processAllInput | +0
02:06:DEBUG:>> 2888 | 1 | NetworkInput::processInput | +15
02:06:DEBUG:>> 2888 | 2 | NetworkInput::processData | +0
02:06:DEBUG:>> 2888 | 3 | NetworkInput::processData | +0
02:06:DEBUG:>> 2888 | 4 | NetworkInput::processGameClientData | +0 <-- exception catch point (below is guessed and could be incorrect!)
02:06:DEBUG:>> 2888 | 5 | PacketCharDelete::onReceive | +0
02:06:DEBUG:>> 2888 | 6 | CClient::addDeleteErr | +0
02:06:CRITICAL:"Access Violation" (0x6c9d3), in SUB: NetworkInput::Message::ProcessMessage()
02:06:DEBUG:10a:Parsing Packet len=43 id=0x83 [2017/06/11 02:06:32]
0 1 2 3 4 5 6 7 8 9 A B C D E F
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
0000 83 d8 7d 98 11 f0 93 2d ad c5 a0 2e 84 76 3c 0e ..}....-.....v<.
0010 6c 4d a0 c6 fd 38 be 0b 9f 18 c3 57 13 b5 a0 43 lM...8.....W...C
0020 cc dd 73 ce 94 4d 11 a3 04 2d 78 ..s..M...-x
RE: How can i find out the reason of this debug? - Coruja - 06-11-2017 01:56 PM
these names are the path order that these functions are called on source code
in your example, that the client had sent an packet to server, where the server process this packet, then call PacketCharDelete -> addDeleteErr() -> ProcessMessage(). Maybe it can have more functions after this addDeleteErr() or maybe not, the code won't show more names because the error already had made the code stop its execution
but with these names you can presume that the error is something behind the character deletion packets/functions. Usually these ProcessMessage() errors occur when the message is not formatted correctly on sphere_msgs.scp (eg: the message must have args like %d / %s / etc but the user had removed it)