Register to post in forums, or Log in to your existing account
 

Play RetroMUD
Post new topic  Reply to topic     Home » Forums » CMUD Beta Forum
Guinn
Wizard


Joined: 03 Mar 2001
Posts: 1127
Location: London

PostPosted: Sat Dec 01, 2007 2:04 pm   

[2.16] Mailed to sales: CMUD 2.14a Crash, includes XML and bugreport (Guinn)
 
Just putting a topic here incase Zugg needs any further comment about it

To: sales@zuggsoft.com
Title: CMUD 2.14a Crash, includes XML and bugreport (Guinn)
Sent: Sat 01/12/2007 13:52 GMT

Quote:
I think this is new to 2.14a as it seemed to be working in previous versions.

I have a whoList class that checks who joined a game and who left. Recently it seems to be having problems not only reporting the correct people that are online, but it’s crashing CMUD too. It doesn’t crash instantly, but it’s pretty consistent after a few minutes that it’ll crash.

If you create a new package, make one class inside it and give it the attached XML file
(the button that’s created would go on the right-side of the screen if you adjust it in the general options - button layout section.)

Then connect to Elysium-rpg.com : 7777
login info <snip>
Then once logged in type ‘emug on’
Then just leave it a while and it’ll probably crash.

If you disable the emug class you’ll see what the mud is sending. If the class is enabled it should gag most of that and just report when people have joined or left.
One of the things I’ve noticed is it now seems to be repeatedly showing the same people as having logged on and off when they’ve not actually gone anywhere.

I’ll make a forum post about it too and tag it with the generated ticket reference if you need any more info or for some reason it doesn’t crash for you...
_________________
CMUD Pro, Windows Vista x64
Core2 Q6600, 4GB RAM, GeForce 8800GT
Because you need it for text... ;)

Last edited by Guinn on Mon Dec 10, 2007 4:57 pm; edited 2 times in total
Reply with quote
Guinn
Wizard


Joined: 03 Mar 2001
Posts: 1127
Location: London

PostPosted: Fri Dec 07, 2007 7:24 pm   
 
I'm still getting crashes with this, even after the stringlists seem to be sorted.
Quote:
date/time : 2007-12-07, 19:19:24, 649ms
computer name : LESHUTTLE
user name :
operating system : Windows Vista build 6000
system language : English
system up time : 10 hours 5 minutes
program up time : 7 minutes 34 seconds
processor : AMD Athlon(tm) XP 3200+
physical memory : 138/1023 MB (free/total)
free disk space : (C:) 8.06 GB (D:) 6.36 GB
display mode : 1280x1024, 32 bit
process id : $16a0
allocated memory : 59.44 MB
executable : cMUDPro.exe
exec. date/time : 2007-12-07 18:18
version : 2.16.0.0
madExcept version : 3.0b
contact name :
contact email :
callstack crc : $28617c37, $32c81297, $fd1d2438
exception number : 1
exception class : EAccessViolation
exception message : Access violation at address 00405B80 in module 'cMUDPro.exe'. Read of address 000000F9.

Main ($16a4):
00405b80 +004 cMUDPro.exe System @LStrAsg
00829602 +03e cMUDPro.exe StringBuf 184 +6 AttrNode.Copy
00a17aeb +0c3 cMUDPro.exe term 6463 +20 CopyARec
00a17b45 +01d cMUDPro.exe term 6470 +2 AddAttrRec
00a1e43a +172 cMUDPro.exe term 8485 +26 TTerm.PutText
00a1ef49 +049 cMUDPro.exe term 8669 +2 TTerm.Add
00d35e75 +0b1 cMUDPro.exe MAIN 1573 +8 TMUDForm.OutputStr
00d36168 +0f4 cMUDPro.exe MAIN 1649 +22 TMUDForm.NextMUDLine
00d365dd +019 cMUDPro.exe MAIN 1723 +4 TMUDForm.DoNextLine
00d80701 +039 cMUDPro.exe MAIN 20927 +3 TMUDForm.ProcessMUDNow
00d77f60 +0a0 cMUDPro.exe MAIN 18574 +12 TMUDForm.ExecCommand
00dff829 +0a9 cMUDPro.exe CodeExec 892 +9 ExecMUDCommand
00e051f2 +416 cMUDPro.exe CodeExec 2436 +43 DoDefault
00e06211 +ea5 cMUDPro.exe CodeExec 2701 +249 HandleCom
00e0784c +610 cMUDPro.exe CodeExec 3135 +108 TCodeExec.InternalExecute
00dfe8d5 +071 cMUDPro.exe CodeExec 461 +9 TCodeExec.Execute
00e05676 +30a cMUDPro.exe CodeExec 2479 +27 HandleCom
00e0784c +610 cMUDPro.exe CodeExec 3135 +108 TCodeExec.InternalExecute
00dfe812 +05e cMUDPro.exe CodeExec 437 +8 TCodeExec.Execute
00e00ead +2ad cMUDPro.exe CodeExec 1244 +48 ExecAlias
00e01461 +141 cMUDPro.exe CodeExec 1329 +15 PushPref
00e01a96 +2a2 cMUDPro.exe CodeExec 1433 +45 HandleVar
00e0236a +6be cMUDPro.exe CodeExec 1547 +88 HandleVarRef
00e0777c +540 cMUDPro.exe CodeExec 3114 +87 TCodeExec.InternalExecute
00dfe812 +05e cMUDPro.exe CodeExec 437 +8 TCodeExec.Execute
00df5814 +098 cMUDPro.exe PrefDat 10881 +8 TCacheNode.Execute
00df1d69 +22d cMUDPro.exe PrefDat 9347 +40 PrefRec.InternalExecute
00df1f7b +01f cMUDPro.exe PrefDat 9396 +2 PrefRec.Execute
00d46637 +14f cMUDPro.exe MAIN 6171 +14 TMUDForm.ExecThread
00d4cf69 +4b9 cMUDPro.exe MAIN 8437 +94 TMUDForm.ExecTrig
00d4ab2c +fc8 cMUDPro.exe MAIN 7645 +324 TMUDForm.HandleTrigger
00d49652 +00e cMUDPro.exe MAIN 7147 +1 TMUDForm.UserOutNewLine
00a1f755 +039 cMUDPro.exe term 8869 +3 TTerm.DoTriggerLine
00a1e1b8 +200 cMUDPro.exe term 8439 +34 HandleNewLine
00a1e99f +6d7 cMUDPro.exe term 8563 +104 TTerm.PutText
00a1ef49 +049 cMUDPro.exe term 8669 +2 TTerm.Add
00d35e75 +0b1 cMUDPro.exe MAIN 1573 +8 TMUDForm.OutputStr
00d36168 +0f4 cMUDPro.exe MAIN 1649 +22 TMUDForm.NextMUDLine
00d365dd +019 cMUDPro.exe MAIN 1723 +4 TMUDForm.DoNextLine
004e287f +1df cMUDPro.exe Controls 4645 +53 TControl.WndProc
004e65ae +18e cMUDPro.exe Controls 6342 +33 TWinControl.WndProc
0050368c +478 cMUDPro.exe Forms 3098 +103 TCustomForm.WndProc
004e6180 +034 cMUDPro.exe Controls 6237 +3 TWinControl.MainWndProc
004803f8 +014 cMUDPro.exe Classes 10966 +8 StdWndProc
76293c85 +00a USER32.dll DispatchMessageA
0050b734 +0ac cMUDPro.exe Forms 6873 +13 TApplication.ProcessMessage
0050b77b +00f cMUDPro.exe Forms 6892 +1 TApplication.HandleMessage
0050ba16 +0a6 cMUDPro.exe Forms 6976 +16 TApplication.Run
00e7ac18 +088 cMUDPro.exe cMUDPro 350 +19 initialization
76f93831 +010 kernel32.dll BaseThreadInitThunk
7769a9bb +04b ntdll.dll LdrInitializeThunk

thread $b1c: <priority:15>
776c0f34 +00 ntdll.dll KiFastSystemCallRet
776c068e +0a ntdll.dll NtWaitForMultipleObjects
76f97e03 +00 kernel32.dll WaitForMultipleObjectsEx
76f9814b +13 kernel32.dll WaitForMultipleObjects
76f93831 +10 kernel32.dll BaseThreadInitThunk
7769a9bb +4b ntdll.dll LdrInitializeThunk

thread $16b4: <priority:15>
776c0f34 +00 ntdll.dll KiFastSystemCallRet
776c068e +0a ntdll.dll NtWaitForMultipleObjects
76f97e03 +00 kernel32.dll WaitForMultipleObjectsEx
76f9814b +13 kernel32.dll WaitForMultipleObjects
76f93831 +10 kernel32.dll BaseThreadInitThunk
7769a9bb +4b ntdll.dll LdrInitializeThunk

thread $16c0:
776c0f34 +000 ntdll.dll KiFastSystemCallRet
76293c6f +124 USER32.dll PeekMessageA
76f93831 +010 kernel32.dll BaseThreadInitThunk
7769a9bb +04b ntdll.dll LdrInitializeThunk

UpdateThread ($15b4): <suspended>
776c0f34 +00 ntdll.dll KiFastSystemCallRet
776c054e +0a ntdll.dll NtSuspendThread
76fa4822 +0c kernel32.dll SuspendThread
0047e3d1 +31 cMUDPro.exe Classes 9648 +5 TThread.Suspend
00905526 +6e cMUDPro.exe IdThread 333 +20 TIdThread.Execute
0047deda +36 cMUDPro.exe Classes 9372 +7 ThreadProc
00405acc +28 cMUDPro.exe System ThreadWrapper
76f93831 +10 kernel32.dll BaseThreadInitThunk
7769a9bb +4b ntdll.dll LdrInitializeThunk

thread $16cc:
776c0f34 +00 ntdll.dll KiFastSystemCallRet
776c068e +0a ntdll.dll NtWaitForMultipleObjects
76f97e03 +00 kernel32.dll WaitForMultipleObjectsEx
7629c4b1 +00 USER32.dll MsgWaitForMultipleObjectsEx
76298b7e +1a USER32.dll MsgWaitForMultipleObjects
76f93831 +10 kernel32.dll BaseThreadInitThunk
7769a9bb +4b ntdll.dll LdrInitializeThunk

thread $1688:
776c0f34 +00 ntdll.dll KiFastSystemCallRet
776c069e +0a ntdll.dll NtWaitForSingleObject
76f977ce +7e kernel32.dll WaitForSingleObjectEx
76f9773d +0d kernel32.dll WaitForSingleObject
0045d9a9 +0d cMUDPro.exe madExcept CallThreadProcSafe
0045da21 +45 cMUDPro.exe madExcept ThreadExceptFrame
76f93831 +10 kernel32.dll BaseThreadInitThunk
7769a9bb +4b ntdll.dll LdrInitializeThunk
>> created by Main ($16a4) at:
76266162 +31 ws2_32.dll WSAAsyncGetHostByName

thread $16d0: <priority:1>
776c0f34 +00 ntdll.dll KiFastSystemCallRet
776c00ee +0a ntdll.dll NtRemoveIoCompletion
76f93831 +10 kernel32.dll BaseThreadInitThunk
7769a9bb +4b ntdll.dll LdrInitializeThunk

thread $96c:
776c0f34 +00 ntdll.dll KiFastSystemCallRet
776c00ee +0a ntdll.dll NtRemoveIoCompletion
76f77942 +23 kernel32.dll GetQueuedCompletionStatus
0045d9a9 +0d cMUDPro.exe madExcept CallThreadProcSafe
0045da21 +45 cMUDPro.exe madExcept ThreadExceptFrame
76f93831 +10 kernel32.dll BaseThreadInitThunk
7769a9bb +4b ntdll.dll LdrInitializeThunk
>> created by thread $162c at:
760dc12e +00 RPCRT4.dll


It's the wholist class that's triggering it I'm sure. Let me know if you need me to mail you the exact package I'm using Zugg...
_________________
CMUD Pro, Windows Vista x64
Core2 Q6600, 4GB RAM, GeForce 8800GT
Because you need it for text... ;)
Reply with quote
Guinn
Wizard


Joined: 03 Mar 2001
Posts: 1127
Location: London

PostPosted: Mon Dec 10, 2007 4:56 pm   
 
More on this - The emug class seems to be what causes the crashes, in that if I never turn it on then it never crashes.
However, once things start crashing it's not a trigger within the emug class that causes the crash, it's just a standard prompt trigger

Code:
<trigger trigontrig="false" newline="false" prompt="true" id="63">
  <pattern>^(%d) (%d) ></pattern>
  <value>#VAR cHealth {%1}
#VAR cMana {%2}
#SHOW %cr
#IF ((@cHealth > @mHealth) || (@cMana > @mMana)) {score}</value>
</trigger>



<trigger id="64">
  <pattern>^(%d) (%d) >(*)$</pattern>
  <value>#VAR cHealth {%1}
#VAR cMana {%2}

// To deal with mud output not sending a newline properly.
#IF (%len(%3)) {
  #GAG
  #SHOW %1 %2 >
  #SHOW %3
}
   
#IF ((@cHealth > @mHealth) || (@cMana > @mMana)) {score}</value>
</trigger>



       | a   Elysium |4628 8801 >
0.0003 | j   Elysium >
0.1055 | a   Elysium |
0.0005 | a   Elysium ]4628 8801 >
0.0004 | f   Elysium |  Pattern: ^(%d) (%d) > : (%1=4628, %2=8801)
0.0008 | c   Elysium |  exec : Pattern "^(%d) (%d) >" : #VAR cHealth {%1} #VAR cMana {%2...
29.658 | a   Elysium |4628 8801 >
0.0007 | f   Elysium |  Pattern: ^(%d) (%d) >(*)$ : (%1=4628, %2=8801, %3="")
0.0008 | c   Elysium |  exec : Pattern "^(%d) (%d) >(*)$" : #VAR cHealth {%1} #VAR cMana...
0.0016 | a   Elysium |The Cow nuzzles you with its snout.
0.0000 |


The crash occurred as I received the prompt, and when I tried again it seemed like it was trigger id 63 that was doing it.

crash is as follows

Quote:
date/time : 2007-12-10, 16:53:12, 205ms
computer name : LESHUTTLE
user name :
operating system : Windows Vista build 6000
system language : English
system up time : 6 hours 29 minutes
program up time : 2 hours 41 minutes
processor : AMD Athlon(tm) XP 3200+
physical memory : 522/1023 MB (free/total)
free disk space : (C:) 8.13 GB (D:) 6.44 GB
display mode : 1280x1024, 32 bit
process id : $a30
allocated memory : 61.52 MB
executable : cMUDPro.exe
exec. date/time : 2007-12-07 18:18
version : 2.16.0.0
madExcept version : 3.0b
contact name :
contact email :
callstack crc : $28617c37, $d5dd6ecd, $d5dd6ecd
exception number : 18
exception class : EAccessViolation
exception message : Access violation at address 00405B80 in module 'cMUDPro.exe'. Read of address FFFFFFF9.

Main ($ba4):
00405b80 +004 cMUDPro.exe System @LStrAsg
008295f7 +033 cMUDPro.exe StringBuf 183 +5 AttrNode.Copy
00a17aeb +0c3 cMUDPro.exe term 6463 +20 CopyARec
00a17b45 +01d cMUDPro.exe term 6470 +2 AddAttrRec
00a1e43a +172 cMUDPro.exe term 8485 +26 TTerm.PutText
00a1ef49 +049 cMUDPro.exe term 8669 +2 TTerm.Add
00d35e75 +0b1 cMUDPro.exe MAIN 1573 +8 TMUDForm.OutputStr
00d39296 +066 cMUDPro.exe MAIN 2345 +4 SendBuf
00d39fd5 +b4d cMUDPro.exe MAIN 2610 +222 TMUDForm.ProcessMUDBuffer
00d35f4d +02d cMUDPro.exe MAIN 1594 +1 TMUDForm.ParseOut
00d3604c +048 cMUDPro.exe MAIN 1617 +4 TMUDForm.EchoStr
00d3a95a +132 cMUDPro.exe MAIN 2807 +22 TMUDForm.EchoPas
00d3a779 +049 cMUDPro.exe MAIN 2763 +4 TMUDForm.EchoInfo
00d4e953 +1af cMUDPro.exe MAIN 9046 +30 TMUDForm.MUDSockConnect
00acd4c6 +02a cMUDPro.exe zsockssh 950 +4 TClientSocket.DoConnect
00acd63a +162 cMUDPro.exe zsockssh 1003 +36 TClientSocket.DoOnConnect
00acd476 +02a cMUDPro.exe zsockssh 937 +3 TClientSocket.OnSockMsg
00acd241 +041 cMUDPro.exe zsockssh 876 +4 TClientSocket.WndProc
004803f8 +014 cMUDPro.exe Classes 10966 +8 StdWndProc
76c53c85 +00a USER32.dll DispatchMessageA
0050b734 +0ac cMUDPro.exe Forms 6873 +13 TApplication.ProcessMessage
0050b77b +00f cMUDPro.exe Forms 6892 +1 TApplication.HandleMessage
0050ba16 +0a6 cMUDPro.exe Forms 6976 +16 TApplication.Run
00e7ac18 +088 cMUDPro.exe cMUDPro 350 +19 initialization
77523831 +010 kernel32.dll BaseThreadInitThunk
773ba9bb +04b ntdll.dll LdrInitializeThunk
_________________
CMUD Pro, Windows Vista x64
Core2 Q6600, 4GB RAM, GeForce 8800GT
Because you need it for text... ;)
Reply with quote
Zugg
MASTER


Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA

PostPosted: Tue Dec 11, 2007 6:44 pm   
 
I've managed to get this crash too. Still not exactly sure what is causing it, but I'll take another look at it if I can.
Reply with quote
Larkin
Wizard


Joined: 25 Mar 2003
Posts: 1113
Location: USA

PostPosted: Tue Dec 11, 2007 6:53 pm   
 
These don't look like properly formed XML to me because of the non-encoded > in the patterns and values. I thought this was ironed out in like 2.14?
Reply with quote
Arde
Enchanter


Joined: 09 Sep 2007
Posts: 605

PostPosted: Tue Dec 11, 2007 7:00 pm   
 
Larkin
It is your browser substitute & codes with ><
Click "Quote" and look at the source. Wink
Reply with quote
Larkin
Wizard


Joined: 25 Mar 2003
Posts: 1113
Location: USA

PostPosted: Tue Dec 11, 2007 8:39 pm   
 
Aha! That makes sense. Laughing
Reply with quote
Guinn
Wizard


Joined: 03 Mar 2001
Posts: 1127
Location: London

PostPosted: Thu Dec 13, 2007 10:03 pm   
 
I think this might be fixed in 2.17. I've been online a bit with the wholist class enabled and not seeing any crashes yet. Guessing it might've been the other stringlist problems with normal variable hash tables?
_________________
CMUD Pro, Windows Vista x64
Core2 Q6600, 4GB RAM, GeForce 8800GT
Because you need it for text... ;)
Reply with quote
Zugg
MASTER


Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA

PostPosted: Thu Dec 13, 2007 10:05 pm   
 
Yep, I think so. I tested it using the package file you sent me along with the server login details and I didn't get any crashes either. I didn't add anything to the Version History because I wasn't exactly sure what to cause this. Glad to hear it's fixed on your end too...thanks for letting me know.
Reply with quote
Display posts from previous:   
Post new topic   Reply to topic     Home » Forums » CMUD Beta Forum All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

© 2009 Zugg Software. Hosted by Wolfpaw.net