Author Topic: WCS 1.6.0 - bugs (Read 4398 times)

NewB · « **on:** June 17, 2005, 04:42:58 am »

installed on win98 1st ed. system. on manual exit, close was not clean - caused a page fault error - details not saved in time.

installed on win98SE:
crashed after 1 minute after 1 join, without any commands, msgs or actions.
reopened and it crashed after join and attempt to login

WCS caused an invalid page fault in
module WCS.EXE at 016f:00405b2b.
Registers:
EAX=79727265 CS=016f EIP=00405b2b EFLGS=00010206
EBX=00000000 SS=0177 ESP=00673994 EBP=00678fd4
ECX=00000000 DS=0177 ESI=00000000 FS=1297
EDX=00678be4 ES=0177 EDI=00678bd4 GS=0000
Bytes at CS:EIP:
66 83 38 00 0f 84 aa 00 00 00 05 ca 00 00 00 50
Stack dump:
0000001d 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

This appears to be related to the big MOTD problem. I had used this same config with 1.5.2 before updating and had reduced the size of the MOTD to avoid garbage characters being displayed, crashes on /login etc. It seems that 1.6.0 is even more sensitive to MOTD size as it crashes on /login with the same MOTD text that worked with v 1.5.2

A quick tes showed that an MOTD of 1082 characters worked ok. MOTD with 1354 characters crashed on /login as described. v1.5.2 worked with MOTD of 2325 bytes.

NewB · « **Reply #1 on:** June 17, 2005, 05:32:28 am »

further MOTD size testing on v1.6.0

1087 characters appeared to work ok.

1137 characters resulted in a couple lines of garbage code being displayed - the #c255# trick that worked for me with v 1.5.2 didn't help

1325 characters caused crash at login.

seems to be a buffer overflow or boundary exceeded in the 1087-1137 range, with severity increasing with additional size.

KM · « **Reply #2 on:** June 17, 2005, 08:42:46 am »

damn it... so my attempt at fixing it made it worse? GRR!

I think i'm going to have to try and tackle this problem from a different angle, because the "make sure it has some memory to store the MOTD in" method doesn't seem to be helping!

Anonymous · « **Reply #3 on:** June 17, 2005, 02:23:46 pm »

Quote from: KM

damn it... so my attempt at fixing it made it worse? GRR!

I think i'm going to have to try and tackle this problem from a different angle, because the "make sure it has some memory to store the MOTD in" method doesn't seem to be helping!

seems so.

I just updated to 1.6.0r2
I reloaded my 1.5.2 cfg with an MOTD of 2300 characters.
it loaded ok without any garbage code being displayed.
I then did login and after some delay, it caused a crash, but in a different way than before. This time in crtdll.dll instead of wcs.exe:

WCS caused an invalid page fault in
module CRTDLL.DLL at 0177:7fc3bdad.
Registers:
EAX=000001fc CS=0177 EIP=7fc3bdad EFLGS=00010212
EBX=65724620 SS=017f ESP=0066f284 EBP=7fc4d7e8
ECX=0000007f DS=017f ESI=65724620 FS=3df7
EDX=000001fc ES=017f EDI=004461d0 GS=0000
Bytes at CS:EIP:
f3 a5 8b c8 03 da 83 e1 03 f3 a4 29 54 24 10 29
Stack dump:
0066fdc4 7fc4d7e8 0000001c 0000002c 00000424 00000200 00000424 7fc3bd2d 65724620 000000d4 00000005 7fc4d7e8 024564b8 02455240 0040cbe6 65724620

KM · « **Reply #4 on:** June 17, 2005, 04:37:25 pm »

well, that could be a good or a bad thing...

good that it didn't crash in the same way, bad that it still crashed - lol

tatertot · « **Reply #5 on:** June 18, 2005, 05:00:47 pm »

having similar problem as newb but i dont have a large motd yet i still crash upon attempting to login

tatertot · « **Reply #6 on:** June 18, 2005, 05:37:37 pm »

you know km, changing #NEWLINE# to somthing a lil smaller such as \n or #line# could also help us reduce the amount o characters n the motd ...just a thought