Page 1 of 1
POL097-2006-07-28
Posted: Tue Aug 01, 2006 2:35 pm
by Xandros
I did some testing on the new core today.
Guilds seem to be working fine now. Alas, I still have the problems with
the broken status window that freezes the clients (see
http://forums.polserver.com/viewtopic.php?t=631).
I hope you can take another look at it...
Xandros
Posted: Sun Aug 13, 2006 9:52 pm
by MuadDib
Do me a favor xandros. Use .startlog to capture the packet as it's sent to you. So far things seem find on my end. Will keep trying to reproduce your problem though until then
Posted: Tue Aug 15, 2006 12:26 pm
by Xandros
Here is the log:
Code: Select all
Log opened at Tue Aug 15 22:22:48 2006
Server -> Client: 0x1C, 65 bytes
0000: 1c 00 41 01 01 01 01 01 01 00 03 b2 00 03 53 79 ..A..... ......Sy
0010: 73 74 65 6d 00 00 00 00 00 00 00 00 00 00 00 00 stem.... ........
0020: 00 00 00 00 00 00 00 00 00 00 00 00 49 2f 4f 20 ........ ....I/O
0030: 6c 6f 67 20 66 69 6c 65 20 6f 70 65 6e 65 64 2e log file opened.
0040: 00 ........ ........
Client -> Server: 0xBF, 6 bytes
0000: bf 00 06 00 24 3c ....$<.. ........
Server -> Client: 0xBC, 3 bytes
0000: bc 01 01 ........ ........
Server -> Client: 0x65, 4 bytes
0000: 65 ff 00 00 e....... ........
Client -> Server: 0x34, 10 bytes
0000: 34 ed ed ed ed 04 00 0e ef fc 4....... ........
Server -> Client: 0x11, 88 bytes
0000: 11 00 40 00 0e ef fc 58 61 6e 64 72 6f 73 00 00 ..@....X andros..
0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
0020: 00 00 00 00 00 00 59 00 59 00 01 00 00 64 00 32 ......Y. Y....d.2
0030: 00 32 00 64 00 64 00 1e 00 1e 00 00 0c c7 00 00 .2.d.d.. ........
0040: 01 b3 00 00 dc fa 67 2d ac 27 58 00 f0 a6 5d 00 ......g- .'X...].
0050: ff ff ff ff 2f f8 57 00 ..../.W. ........
Client -> Server: 0xBF, 6 bytes
0000: bf 00 06 00 24 50 ....$P.. ........
Client -> Server: 0xBF, 6 bytes
0000: bf 00 06 00 24 27 ....$'.. ........
Server -> Client: 0xBC, 3 bytes
0000: bc 01 01 ........ ........
Server -> Client: 0x65, 4 bytes
0000: 65 ff 00 00 e....... ........
Client -> Server: 0x2, 7 bytes
0000: 02 04 07 00 00 00 00 ........ ........
Server -> Client: 0x22, 3 bytes
0000: 22 07 01 "....... ........
Client -> Server: 0x2, 7 bytes
0000: 02 04 08 00 00 00 00 ........ ........
Server -> Client: 0x22, 3 bytes
0000: 22 08 01 "....... ........
Client -> Server: 0x2, 7 bytes
0000: 02 04 09 00 00 00 00 ........ ........
Server -> Client: 0x22, 3 bytes
0000: 22 09 01 "....... ........
Client -> Server: 0x2, 7 bytes
0000: 02 04 0a 00 00 00 00 ........ ........
Server -> Client: 0x22, 3 bytes
0000: 22 0a 01 "....... ........
Client -> Server: 0xBF, 6 bytes
0000: bf 00 06 00 24 7d ....$}.. ........
Client -> Server: 0xBF, 9 bytes
0000: bf 00 09 00 0c 00 0e ef fc ........ ........
Server -> Client: 0xBC, 3 bytes
0000: bc 01 01 ........ ........
Server -> Client: 0x65, 4 bytes
0000: 65 ff 00 00 e....... ........
Server -> Client: 0xAA, 5 bytes
0000: aa 00 00 00 00 ........ ........
Log closed at Tue Aug 15 22:23:05 2006
I started the log, then opened the status window, which didn't
show any values. Then the client was frozen and I logged out.
Thanks,
Xandros
Posted: Sun Aug 20, 2006 9:46 am
by Rimmon
fresh pol097 core crashes:
dunno why r these crashes happen, maybe the same error on all dumps
as for me, the new core is very unstable
dumps r here:
http://radigost.com/dumps.zip
Posted: Sun Aug 20, 2006 1:32 pm
by CWO
You should post whats in the pol.log. It should also give you a script name and PC. You should go to that script and find its listing (its the script name with a .lst extension). If you dont have it, compile the script again with ecompile using -l as an arguement or set GenerateListing 1 in your ecompile.cfg. With the .lst file, open it up in a text editor and look for the PC number and post from a few lines before that to a few lines after. If you're having trouble with this, look at what other people post with their crash dumps.
Posted: Fri Aug 25, 2006 11:32 pm
by MuadDib
Who knows, think I got it kicked out. Seems to be anyway hehe.
Was an issue involving the padding for the non-aos status bars.
Should be resolved in next beta
Posted: Sat Aug 26, 2006 3:14 am
by Xandros
Thanks
