Author Topic: WCS (Read 57870 times)

KM · « **Reply #100 on:** May 14, 2006, 08:41:08 pm »

look... erm, on this page... lol

at least gnarly had the excuse that it was the previous page

GhostShip · « **Reply #101 on:** May 15, 2006, 09:30:13 am »

New betas out folks

http://www.kingmacro.net/files/wcs-1.8b4-win32.zip

And for Linux users

http://www.kingmacro.net/files/wcs-1.8b4-linux.gz

Quote

WCS 1.8b4 is availiable for testing,

If you are just looking to get WCS for your room then DO NOT GET THIS, go to the WinMX Section and download the latest WCS Version from there as this is a BETA VERSION and I can almost guarantee bugs!

OK, here is beta 4, changes since beta 3?
+ a few more attempts at fixing that crashing bug (let's see shall we... lol)
+ added cacheless running (contains an internal cache, so instead of constantly checking with the caches every 10 primary connections it uses an internal cache) - still needs a cache to connect of course
+ added connection cycling - after a while it will disconnect primary connections (even if they are operational) just in case of unknown errors
+ added the date to the output in the win32 version, and added the time/date to the unix versions output
+ added licence agrement

Some interesting additions there

Cheers KM

KM · « **Reply #102 on:** May 15, 2006, 08:20:28 pm »

oops... except i forgot to post the licence agrement with it... oh well, a minor point, guess b5 will have to have it instead... lol

~~GnarlySnarly~~ · « **Reply #103 on:** May 16, 2006, 05:11:25 am »

Quote from: GhostShip on May 15, 2006, 09:30:13 am

New betas out folks

http://www.kingmacro.net/files/wcs-1.8b4-win32.zip

And for Linux users

http://www.kingmacro.net/files/wcs-1.8b4-linux.gz

Quote
WCS 1.8b4 is availiable for testing,

If you are just looking to get WCS for your room then DO NOT GET THIS, go to the WinMX Section and download the latest WCS Version from there as this is a BETA VERSION and I can almost guarantee bugs!

OK, here is beta 4, changes since beta 3?
+ a few more attempts at fixing that crashing bug (let's see shall we... lol)
***
+ added licence agrement

I started a session of beta 3, testing with just a few people in the room, iow little or not activity., then left town.
When I returned some days later I saw that it had crashed after about 28 hours. Didn't quite make it to 49.7 days

WCS caused a stack fault in module WCS.EXE at 017f:0040322a.
Registers:
EAX=b9123690 CS=017f EIP=0040322a EFLGS=00010212
EBX=00000003 SS=0187 ESP=005a1e2c EBP=005a2240
ECX=005a2234 DS=0187 ESI=00000001 FS=31cf
EDX=00000046 ES=0187 EDI=0044714c GS=0000
Bytes at CS:EIP:
53 56 57 8b 75 08 69 c6 30 04 00 00 8d 3c 05 1c
Stack dump:
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

not sure if that is related to the 'crashing bug' KM was trying to fix.

as to the license, screw that.. i'll stick with v 1.7.4 :p I'm a confirmed scoflaw! hehe

nylly444 · « **Reply #104 on:** May 16, 2006, 04:28:06 pm »

beta4 unix still crashes after a few hours.
Been running it in offline mode for 20+ on my home machine and 3+ hours on our server now though and it seems fine.
Hope that narrows it down a bit...

Snick · « **Reply #105 on:** May 16, 2006, 04:53:20 pm »

Sharegaurd has trouble on 1 digit ports... try hosting your room on port 6698 or something with 3 or 4 digits.

KM · « **Reply #106 on:** May 16, 2006, 07:10:04 pm »

Quote from: nylly444 on May 16, 2006, 04:28:06 pm

beta4 unix still crashes after a few hours.
Been running it in offline mode for 20+ on my home machine and 3+ hours on our server now though and it seems fine.
Hope that narrows it down a bit...

unfortunately it does narrow it down - to somewhere in the 500 odd lines of code for channel listings, lol

goto job though, because if it turned out to be somewhere in the main code for dealing with clients... that spans several files, each of which are several times the size of the file that deals with listings

however i don't understand the windows version also having that bug, as very little was changed from 1.7.4 in that section of code... although i guess that could help narrow it down

nylly444 · « **Reply #107 on:** May 16, 2006, 07:29:04 pm »

21:10:26 Channel Uptime: 0d 23h 28m 8s

oh, one other thing: I now even get a log file with something in it...

~~GnarlySnarly~~ · « **Reply #108 on:** May 16, 2006, 07:46:50 pm »

Quote from: nylly444 on May 16, 2006, 04:28:06 pm

beta4 unix still crashes after a few hours.
Been running it in offline mode for 20+ on my home machine and 3+ hours on our server now though and it seems fine.
Hope that narrows it down a bit...

win98se also
dialup mode, with 2 or 3 idle users

wcs uptime: 27 min:

01:19:44 This Channel is hosted on WCS 1.8b4-Win32
***
01:46:54 You left the channel.

WCS caused a stack fault in module WCS.EXE at 017f:00403235.
Registers:
EAX=1d860ffd CS=017f EIP=00403235 EFLGS=00010212
EBX=00000003 SS=0187 ESP=005a1e2c EBP=005a2240
ECX=00000000 DS=0187 ESI=00000000 FS=1917
EDX=00000000 ES=0187 EDI=00446d1c GS=0000
Bytes at CS:EIP:
53 56 57 8b 75 08 6a 00 e8 b2 10 01 00 69 c6 34
Stack dump:
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

KM · « **Reply #109 on:** May 17, 2006, 02:08:48 am »

and naturally i am still unable to get WCS to crash on any of my test systems (or virtual test systems)... i blame everyone else

still trying to find any possible crash reasons in the primary code :-S

~~GnarlySnarly~~ · « **Reply #110 on:** May 17, 2006, 03:55:34 am »

Quote from: KM on May 17, 2006, 02:08:48 am

and naturally i am still unable to get WCS to crash on any of my test systems (or virtual test systems)... i blame everyone else

still trying to find any possible crash reasons in the primary code :-S

you gotta use the canary system, designed for stability testing.. win 98

do these snippets help?

crash 3 ==============
uptime:
1:47:05

15:02:26 This Channel is hosted on WCS 1.8b4-Win32
***
16:49:31 You left the channel.

WCS caused an invalid page fault in
module KERNEL32.DLL at 017f:bff7a189.
Registers:
EAX=00000001 CS=017f EIP=bff7a189 EFLGS=00010202
EBX=097e7744 SS=0187 ESP=00693970 EBP=097e7740
ECX=00470000 DS=0187 ESI=00483118 FS=329f
EDX=cc76cdc0 ES=0187 EDI=0936462c GS=0000
Bytes at CS:EIP:
89 75 00 83 c1 08 80 0b 02 39 39 73 07 83 c1 10
Stack dump:
006939a4 00483118 00470000 00000580 bff7b31d 00470000 00483118 000014fc 00000200 00000064 0048311c 00000580 00483118 00693e54 7fc0b9e0 00470000

crash 4==============
uptime: 54 min.

21:15:53 This Channel is hosted on WCS 1.8b4-Win32
***
22:09:28 You left the channel.

WCS caused a stack fault in module WCS.EXE at 017f:00403235.
Registers:
EAX=00000013 CS=017f EIP=00403235 EFLGS=00010202
EBX=00000003 SS=0187 ESP=005a1e20 EBP=005a2234
ECX=005a2234 DS=0187 ESI=00000001 FS=3d97
EDX=00000000 ES=0187 EDI=00447150 GS=0000
Bytes at CS:EIP:
53 56 57 8b 75 08 6a 00 e8 b2 10 01 00 69 c6 34
Stack dump:
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

~~GnarlySnarly~~ · « **Reply #111 on:** May 17, 2006, 04:29:19 am »

of the 6 crashes i logged, only 1 involved 'invalid page fault' in kernel32.exe. the others were all stack faults with wcs.exe

after crash 6, i edited the config to go offline. any other config changes that might help narrow things down?
if these copied details don't help much, lemme know, and i'll stop posting them. If there are any other things i can do to better document the crashes for you, lemme know that too, as it seems i can get a crash within 2 hours.

crash 5:

uptime: ~ 3 min.
no details copied.

crash 6:
uptime: < 8 min.

00:00:31 This Channel is hosted on WCS 1.8b4-Win32
***
00:07:54 You left the channel.

crashed while trying to open config.ini

WCS caused a stack fault in module WCS.EXE at 017f:00403235.
Registers:
EAX=00000013 CS=017f EIP=00403235 EFLGS=00010202
EBX=00000003 SS=0187 ESP=005a1e20 EBP=005a2234
ECX=005a2234 DS=0187 ESI=00000000 FS=481f
EDX=00000000 ES=0187 EDI=00446d1c GS=0000
Bytes at CS:EIP:
53 56 57 8b 75 08 6a 00 e8 b2 10 01 00 69 c6 34
Stack dump:
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

KM · « **Reply #112 on:** May 17, 2006, 05:43:04 pm »

actually, no those don't help, only time they are useful is if something is written in ASM, which WCS isn't... amazing just how useless microsoft error messages are

i am trying to get it to crash... it's extremely stable here, lol

String · « **Reply #113 on:** May 17, 2006, 11:12:00 pm »

The last error is due to stack overflow or overwrite. It's detected just looking at the value in the ESP and EBP registers.
In such a case the ESP register is slightly smaller than EBP, smaller than the limit of the SS segment, and larger than EIP.

From the web i found "...overwriting the stack, e.g. by writing (assigning values) to array elements beyond the array limits, or due to incorrect argument list passed to a function, like passing a pointer to an int to a function that expects a pointer to an double, or passing buffers to a library function without sufficient space to hold the results..." :shock:

The EIP register stores the address where the error occurred.

Anyway if it's not Broken, don't Fix it !

KM · « **Reply #114 on:** May 17, 2006, 11:30:46 pm »

yes, they nearly all are buffer overflows - which is a pain considering the only buffer in the primary connection code that could possibly overflow as far as i can tell would be the 1024 byte receive buffer, which will never receive that much (and can't due to limitations in the primary receive code), lol

however, for some odd reason just as i came to read this thread WCS crashed - is that considered good or bad? lol - it was running under a debugger, which gave a lot of info - turns out that the debugger in lcc is a load of...

* KM starts trying other debuggers, lol

~~GnarlySnarly~~ · « **Reply #115 on:** May 18, 2006, 05:43:28 am »

When i tried to open the config.ini file through the wcs menu, crash 6 resulted as reported above.. maybe a coincidence..
I was trying to edit my config to go offline, which i did and then restarted wcs after that crash.

01:34:41 Host Uptime: 7d 16h 18m 31s
01:34:41 Channel Uptime: 1d 0h 33m 13s

offline, it seems to be going strong a day later.
but it did run for 27 hours online when i first installed it, so who knows..

I think i can get quick crashes, but wouldn't know how to capture more useful debug data that might help you track this one down. If you have some suggestions on that, i'll do my best to crash it again

~~GnarlySnarly~~ · « **Reply #116 on:** May 19, 2006, 05:00:44 am »

well it ran 40+ hours offline, before i crashed the system doing something else

~~GnarlySnarly~~ · « **Reply #117 on:** May 24, 2006, 01:06:01 am »

Quote from: GnarlySnarly on May 19, 2006, 05:00:44 am

well it ran 40+ hours offline, before i crashed the system doing something else

20:58:23 Host Uptime: 4d 20h 48m 30s
20:58:23 Channel Uptime: 4d 20h 45m 34s

running offline, it likely would have been up nearly a week had something else not crashed the system.

seems to confirm the theory that something in the connection to wpn is causing the crashes.

Mari Jane · « **Reply #118 on:** June 05, 2006, 09:33:32 pm »

WCS .....got wcs goin..but whenever some chats..they get message block...any help?

*^*Åü§§ïëgïrl*^* · « **Reply #119 on:** June 06, 2006, 03:50:01 am »

In the wcs config file make sure there isn't an empty block= when you're editing what words you wish to block..
eg:

Block=@hotmail.com
Block= <--- that empty space will produce a block message every time someone chats (except opchats)

Author Topic: WCS (Read 57870 times)

KM

KM

Snick

KM

KM

KM

KM