eva收到群消息的时候崩溃
崩溃时，命令行留下来的输出Got server :202.96.170.164
EvaMain::slotSetupEvaClient
password key set!
EvaMain::slotFriendListReady
got login token
login token set!
password key set!
InPacket->decryptBody: session key not set yet, set decrypted
length to 0
Bad packet, ignore it
session key set!
file session key set!
file share token set!
client key set!
user "1159615" logged in!
EvaPacketManager::slotClientNotReady ----- QQ_CMD_REQUEST_KEY
got keys reply
file agent key set!
76585270664a3735424b4d3975636b79
file agent token set!
30a83a8cb35b18f98bd2c09ef37f3cf25efe5fbbcc194fec2037289327b6c
19bb2103aab4f706a98e3bdcb689337be91dd92221d50c6d361
change status reply
user info
user login process done!
friend change status
got keys reply
file agent key set!
51484673334b526b38516d6d67434954
file agent token set!
1a35ef861767f1ab82f526e8b7 14612ad671c4dcf30ee928861cc1e8a22
03710c6fb7caacdc0ba8dbfdc9e266ce6a8fd80e59bc0fdf1b5
got level reply
got level reply
got extra info reply
EvaUHManager::cleanUp
EvaUHManager::doDnsRequest -- waiting DNS
EvaUHManager::slotDnsReady ---- got
got signature op reply
EvaUHManager::cleanUp
received new message
IM: seq: 922315 ----- msg seq: -4515
Unknow IM Type: 0x12
sender: 10000, receiver: 1159615, sender IP: 219.133.49.165, sender port: 8000
version:0x 100, command: 0x17, sequence: 0xffffee5d
after InPacket headr(7(UDP) or 9(TCP) bytes) plus ReceiveIMPa cket header(20 bytes):
0:00 27 100 11 b1 bf
8:0e 12 cb db 85 31 a5
16: 1f 400 122
============================
got Qun operation reply
got Qun operation reply
KCrash: Application 'eva' crashing...
如果需要进一步的信息，如何提供请说明。 说实在话，我感觉EVA还不如LUMA来得稳定些。
不要问我哪方面不稳定之类的话，因为这是我实际使用得出的结论。 是报错的人多吧。
呵呵，大家一起来找BUG。
页:
[1]