Release: UTDC v1.8

[pLaYa]

Possessed PlayerPawn: bbTFemale2 CTF-Control.bbTFemale1
Join succeeded: pappy
Signal: SIGSEGV [segmentation fault]
Aborting.
Exiting.
Name subsystem shut down
Allocation checking disabled


Now my server crashes randomly when anyone joins.. 2 x in less then an hour... Running SWA new test version and UTDC v1.8..... I'm ready to ditch utdc... i'd rather put up with cheaters then have my server crashing every 5 mins

[Al]

http://en.wikipedia.org/wiki/SIGSEGV

?

I have no idea what it means. Old software on your server?

That person could very well be a cheater, IMO. Or a hacker?

SIGSEGV is usually generated by the operating system, however users with appropriate permissions can use the kill() system call, or kill command (userland program, or sometimes a shell builtin) to send the signal to a process at will.

[pLaYa]

GRRR there not hackers.... there my clan mates... there far from hackers with the way some of them play.... This is a UTDC issue... the crash always happens midgame(normally after a long period of anyone joining).... i down graded SWA since that seems to be a issue with UTDC.... and since when is UTDC suppost to crash everytime a cheater joins? if this doesn't work i'm ditchin UTDC cause right now it isn't the cheaters pissing everyone off on my server... its UTDC

I just downgraded SWA to 095 working good so far..

Update: well even the test version of SWA isn't right... cause now that i downgraded to 0.95 it hasn't crashed at all yet... before it was crashing 2-3 times per hour... Rush what ya thinkin? I wish i could provide u with better error messages but i don't have any :/

[DonutHunter]

I'm very happy with .095....sometimes stability is more important than bleeding edge, especially if the Doctor's can't figure out what to do!

-:-)

[pLaYa]

Yes 097 is a huge improvement.... I think a feature should be added to SWA to disable ALL UTDC features.... not everyone uses UTDC.. plus everytime theres an update to UTDC it will most likly break things...

[Obsidian]

When you don't use UTDC you don't install it. Why are you installing software just so you can disabled everything it does?

It was already posted why it crashes. That has nothing to do with new releases causing the same problems but all with relying on variables being set properly without checking.

[Rush]

Originally Posted by pLaYa

Possessed PlayerPawn: bbTFemale2 CTF-Control.bbTFemale1
Join succeeded: pappy
Signal: SIGSEGV [segmentation fault]
Aborting.
Exiting.
Name subsystem shut down
Allocation checking disabled

This error shows that it's rather some native fault than SWA's ... Is it even possible to trigger such error with uscript ?

Originally Posted by pLaYa

Yes 097 is a huge improvement.... I think a feature should be added to SWA to disable ALL UTDC features.... not everyone uses UTDC.. plus everytime theres an update to UTDC it will most likly break things...

What features ? SWA supports ONLY screenshot stuff, that is:
-it marks Linux/Mac users as not being able to take shots basing on UTDC's messages
-it places "UTDC Shot" buttons on the playerlist. If clicked, SWA then triggers the shot command and basing on UTDC's output it displays various "states" in the shot window, fortunately, in the end SWA can decode the screenshot file using Base64 algorithm(it's not even the native one in ut, it's my own, scripted) and send it through the socket as a jpg file. And this all stuff is running only on the CLICK, not AFTER JOIN.

I hope I'm not wrong this time as I was with the previous crash, but that time I fixed the bug immediately after a crashlog .. this log doesn't show it's SWA's fault.
edit: http://lux.one.pl/~rush/ut/SWA097c-test3.zip - try this, but note that if it fixes the problem it would still be the engine's fault.

[face]

look on page 3 rush i posted againa new crash code.

[Matthew]

Rush - maybe if this build yeilds issues still, you could try putting in what I use in test code, called MARK points. For instance, before a function is started I put in Log("MARK 1"); or MARK 2, etc etc - then if a crash occurs, the function which caused the issue can be traced. Just an idea.

So maybe in function AddMessage before pos=InStr(S," is not being checked because of uncompatible OS"); and another after SWA.SetUncompatibleOS(Mid(Left(S,pos), 15));, then in UncompatibleOS and so on


But anyway I've been looking through the code as well, and Rush's coding skills are quite sound - I cannot see any reason why it would crash either, and considering it's a segmentation fault, it will be hard to trace. At least in UScript-related crashing, the log can provide a class and function name.

[Rush]

Matthew actually I started thinking that the last crash might be affected by checking for new players in the Tick function, I was doing:

function Tick(float DeltaTime)
{
   if(Level.Game.CurrentID > CurrentID)
   {
       (Player Initialization)
       CurrentID=Level.Game.CurrentID;
   }
}

but for example BDBMapVote is doing it this way:

function Tick(float DeltaTime)
{
   if(Level.Game.CurrentID > CurrentID)
   {
      if(JoinTickCount < 20)  // added 20 tick delay too see if it reduces intermittant crash problem
      {
         JoinTickCount++;
         return;
      }
      JoinTickCount=0;
       (Player Initialization)
       CurrentID=Level.Game.CurrentID;
   }
}

the comment is a quota from BDBMapVote's code .. I added such delay to the newest SWA build.
PS. Respect on finding your way through SWA's mess

[face]

Well i got it all of my server now and the pings are good again no lagg no crashes so i just leave it this way and just use eut.

Sorry for this,but if utdc would work better no screen like on 15 fps and no more crashes then i will use it.Till then it stays of my servers.

I work too and i do not have time to reset my stuff like 3 or 4 times a day,i am happy people spending time on this to make things good for the server owners and against cheaters,but i need a solid programm to use if you know what i mean.

Thx anyway.

[Matthew]

Originally Posted by Rush

PS. Respect on finding your way through SWA's mess

You code like I do - nice and neat with proper bracket and tabbing; it's very easy to read and follow

[Troublesome]

Originally Posted by face

I work too and i do not have time to reset my stuff like 3 or 4 times a day,i am happy people spending time on this to make things good for the server owners and against cheaters,but i need a solid programm to use if you know what i mean.

Thx anyway.

this mod is used on many servers without problems. my own clanserver have never chrashed - however i have never advised to put it on public servers cus of installation and possible problems with less used os and dumbass admins who cant take the time to read the readme.txt if u know what i mean

[Al]

Never had any problems here either Troublesome.

[face]

Well maybe its used on many servers but i want to use it with swa97 and there is the problem till swa95 its ok but after that it crashes a lot.

No need to read the read me on that if you see the code i put up you see the problem if not then to bad and i won't use it.Ill find other programms then.

[Matze]

To the SWA Problem it must be something in combination of both, since i downgraded to 0.95 i had only 1 crash in 12 days.

I got also some Logs with Corrupted Memory for Players that normal didnt had this issue :

[UTDCv18] +---------------------------------------------------+
[UTDCv18] Client have corrupt memory
[UTDCv18] Player name......: *
[UTDCv18] Player IP........: *
[UTDCv18] Client UT version: v.4.36
[UTDCv18] Client OS........: WindowsXP
[UTDCv18] Corruption hash..: BBF0ECD68A5C581AD518DE42A640C3CA
[UTDCv18] Altered addresses: 7C90DD78-FF909090/B8909090,7C90DD7C-E001E25/7A,7C90DD80-FE03005F/FE0300BA,
[UTDCv18] Date/Time........: 29-04-2006 / 19:07:21
[UTDCv18] +---------------------------------------------------+ 

[UTDCv18] +---------------------------------------------------+
[UTDCv18] Client have corrupt memory
[UTDCv18] Player name......: *
[UTDCv18] Player IP........: *
[UTDCv18] Client UT version: v.4.36
[UTDCv18] Client OS........: WindowsXP
[UTDCv18] Corruption hash..: 1CBDD26EC151761276D5D3AED2E5FF80
[UTDCv18] Altered addresses: 7C90D974-BF689090/49B89090,7C90D978-C300CD13/BA000000,7C90DF5C-39689090/91B89090
,7C90DF60-C300CD15/BA000000,7C90E1A8-68689090/ADB89090,7C90E1AC-C300CD12/BA00000
0,
[UTDCv18] Date/Time........: 30-04-2006 / 15:07:09
[UTDCv18] +---------------------------------------------------+ 

[UTDCv18] +---------------------------------------------------+
[UTDCv18] Client have corrupt memory
[UTDCv18] Player name......: *
[UTDCv18] Player IP........: *
[UTDCv18] Client UT version: v.4.36
[UTDCv18] Client OS........: WindowsXP
[UTDCv18] Corruption hash..: 831C158DDE8F351C68EE5444405F7247
[UTDCv18] Altered addresses: 77F469D0-3EE9E4EB/5868E4EB,77F469D4-68880C96/68000002,
[UTDCv18] Date/Time........: 30-04-2006 / 15:29:48
[UTDCv18] +---------------------------------------------------+ 

[UTDCv18] +---------------------------------------------------+
[UTDCv18] Client have corrupt memory
[UTDCv18] Player name......: *
[UTDCv18] Player IP........: *
[UTDCv18] Client UT version: v.4.36
[UTDCv18] Client OS........: WindowsXP
[UTDCv18] Corruption hash..: EF7E08855388D922CE3786890B2C4EA3
[UTDCv18] Altered addresses: 77F4B6B8-1E25FF/3FB8,77F4B6BC-3005F0B/300BA00,77F4B6D8-1E25FF/41B8,77F4B6DC-3005
F0E/300BA00,77F4C238-1E25FF/F7B8,77F4C23C-3005F11/300BA00,
[UTDCv18] Date/Time........: 30-04-2006 / 19:50:15
[UTDCv18] +---------------------------------------------------+ 

[UTDCv18] +---------------------------------------------------+
[UTDCv18] Client have corrupt memory
[UTDCv18] Player name......: *
[UTDCv18] Player IP........: *
[UTDCv18] Client UT version: v.4.36
[UTDCv18] Client OS........: WindowsXP
[UTDCv18] Corruption hash..: AA954EFEEE898F8E8D7E644F4DA13D70
[UTDCv18] Altered addresses:
77F55668-1E25FFE4/25868E4,77F5566C-685F4100/68680000,77F758A8-25FF0004/19B80004,
77F758AC-5F44001E/BA000000,77F7595C-25FF000C/25B8000C,77F75960-5F4A001E/BA000000
,77F75998-25FF000C/29B8000C,77F7599C-5F47001E/BA000000,77F75AD4-1E25FF00/3EB800,
77F75AD8-5F5000/BA0000,77F75AE4-1E25FF/3FB8,77F75AE8-3005F4D/300BA00,77F75B00-25
FF000C/41B8000C,77F75B04-5F53001E/BA000000,77F75B5C-1E25FF/47B8,77F75B60-3005F56
/300BA00,77F75B78-25FF000C/49B8000C,77F75B7C-5F59001E/BA000000,77F75DF8-FF000CC2
/B8000CC2,77F75DFC-5F001E25/74,77F75E00-FE03005F/FE0300BA,77F75E28-1E25FF/77B8,7
7F75E2C-3005F5C/300BA00,77F7608C-FF0014C2/B80014C2,77F76090-62001E25/A0,77F76094
-FE03005F/FE0300BA,77F7618C-25FF000C/B1B8000C,77F76190-5F65001E/BA000000,77F761E
8-1E25FF/B7B8,77F761EC-3005F68/300BA00,77F7644C-FF0014C2/B80014C2,77F76450-6B001
E25/E0,77F76454-FE03005F/FE0300BA,77F765A8-1E25FF/F7B8,77F765AC-3005F6E/300BA00,
77F76738-FF0004C2/B80004C2,77F7673C-71001E25/112,77F76740-FE03005F/FE0300BA,
[UTDCv18] Date/Time........: 30-04-2006 / 22:03:13
[UTDCv18] +---------------------------------------------------+ 

[UTDCv18] +---------------------------------------------------+
[UTDCv18] Client have corrupt memory
[UTDCv18] Player name......: *
[UTDCv18] Player IP........: *
[UTDCv18] Client UT version: v.4.36
[UTDCv18] Client OS........: WindowsXP
[UTDCv18] Corruption hash..: 82B03FD0CA009A216AC21C7628AB02F6
[UTDCv18] Altered addresses:
7C90D8A4-1E25FF/3FB8,7C90D8A8-3005F0B/300BA00,7C90D8CC-25FF9090/41B89090,7C90D8D
0-5F0E001E/BA000000,7C90E7BC-1E25FF/F7B8,7C90E7C0-3005F11/300BA00,
[UTDCv18] Date/Time........: 01-05-2006 / 17:02:55
[UTDCv18] +---------------------------------------------------+ 

[UTDCv18] +---------------------------------------------------+
[UTDCv18] Client have corrupt memory
[UTDCv18] Player name......: *
[UTDCv18] Player IP........: *
[UTDCv18] Client UT version: v.4.36
[UTDCv18] Client OS........: WindowsXP
[UTDCv18] Corruption hash..: E19835BDC650B2A052165B2B584C94EC
[UTDCv18] Altered addresses:
7C9037B8-EBE80875/4D8B0875,7C9037BC-64848AC9/64D1FF18,
[UTDCv18] Date/Time........: 01-05-2006 / 19:41:28
[UTDCv18] +---------------------------------------------------+

[UTDCv18] +---------------------------------------------------+
[UTDCv18] Client have corrupt memory
[UTDCv18] Player name......: *
[UTDCv18] Player IP........: *
[UTDCv18] Client UT version: v.4.36
[UTDCv18] Client OS........: WindowsXP
[UTDCv18] Corruption hash..: 91AA3E315E630670D30E3D2341FDF5B0
[UTDCv18] Altered addresses:
7C91D7D0-80E99090/35B89090,7C91D7D4-BA838228/BA000000,7C9261C8-41E99090/6C689090
,7C9261CC-6883819F/68000002,
[UTDCv18] Date/Time........: 01-05-2006 / 20:08:54
[UTDCv18] +---------------------------------------------------+ 

[UTDCv18] +---------------------------------------------------+
[UTDCv18] Client have corrupt memory
[UTDCv18] Player name......: *
[UTDCv18] Player IP........: *
[UTDCv18] Client UT version: v.4.51b
[UTDCv18] Client OS........: WindowsXP
[UTDCv18] Corruption hash..: 93D83C4BB698D55A9002475FCB4A4B47
[UTDCv18] Altered addresses:
7C91D94C-6E4570E9/47B8,7C91D950-300BA93/300BA00,7C91D974-E7E99090/49B89090,7C91D
978-BA936E42/BA000000,7C91DF5C-A8E99090/91B89090,7C91DF60-BA936E3A/BA000000,7C91
E1A8-6CE99090/ADB89090,7C91E1AC-BA936E37/BA000000,
[UTDCv18] Date/Time........: 01-05-2006 / 20:34:29
[UTDCv18] +---------------------------------------------------+

[Destiny]

Originally Posted by Troublesome

this mod is used on many servers without problems. my own clanserver have never chrashed - however i have never advised to put it on public servers cus of installation and possible problems with less used os and dumbass admins who cant take the time to read the readme.txt if u know what i mean

ReadMe.txt

------------------- Misc Commands -------------------
*mutate utdc set allow all os off
-This will turn utdc protection on for all clients and reject linux and mac os clients.

Will it reject WindowsXP x64 too ?
Or you already have reports of UTDCv1.8 working fine with WindowsXp x64 clients?
OSCare=True by default.... in the ini.
Atleast I really don't know what u mean by "u know what i mean".

[Troublesome]

Originally Posted by Destiny

ReadMe.txt

Will it reject WindowsXP x64 too ?
Or you already have reports of UTDCv1.8 working fine with WindowsXp x64 clients?
OSCare=True by default.... in the ini.
Atleast I really don't know what u mean by "u know what i mean".

you can donate winxp 64 to me and i will maby look into it. other than that theres no support other than what i feel motivated for or from the good ppl of this forum. ppl can chose use it or not...

[Rush]

Originally Posted by Troublesome

you can donate winxp 64 to me and i will maby look into it. other than that theres no support other than what i feel motivated for or from the good ppl of this forum. ppl can chose use it or not...

And what if you could find a person with winxp 64 that would actively test your work and provide you with all the winxp 64 stuff you need ? ... I bet that people on this forum would be delighted to help you.

[Destiny]

Thanks for the reply Troublesome....hmph Finally

I din't know if its that difficult to recompile the .u files to exclude x64.
Surprisingly, previous versions of UTDC DLLs are compatible with that OS.
I bet its a new API call thats causing the problem.
Don't fall for people bitching, some ppl always do. UTDC v1.7 also wasn't perfect when it came out, until v1.7b. It takes a lot of time and effort to support a dying game.
I appreciate it!