 |
Vijilante
SubAdmin
Joined: 18 Nov 2001
Posts: 5187
|
 Posted: Sat Dec 01, 2007 4:04 pm
[2.14] Crash with silly alarm
|
I haven't been able to replicate this one. I was tweaking around with a silly alarm that tries to use threads and sections as a counter so it is doing all sorts of weird stuff. This was also bumping into the #T- failure which just added to the weirdness.
| Code: |
<?xml version="1.0" encoding="ISO-8859-1" ?>
<cmud>
<trigger name="Example1" type="Alarm" priority="10" enabled="false">
<pattern>*1</pattern>
<value>#THREAD ex1 {#SECTION Ex1 {#WAITSIGNAL ex1;#SIGNAL ex1}}
#SHOW I am example alarm 1, I have fired %section(Ex1) times.
#IF (%section(Ex1)>=5) {
#SHOW "That was 5, I will shut off shortly."
#T- Example1
#SIGNAL ex1
}</value>
</trigger>
</cmud> |
| Code: |
date/time : 2007-12-01, 10:32:52, 653ms
operating system : Windows XP Service Pack 2 build 2600
system language : English
system up time : 43 days 3 hours
program up time : 2 hours 4 minutes
processor : AMD Athlon(tm) Processor
physical memory : 115/383 MB (free/total)
free disk space : (C:) 14.29 GB
display mode : 1024x768, 32 bit
process id : $c584
allocated memory : 49.26 MB
executable : cMUD.exe
exec. date/time : 2007-11-30 23:53
version : 2.14.0.1
madExcept version : 3.0b
callstack crc : $6063e05f, $ed59b033, $ed59b033
count : 2
exception number : 1
exception class : EAccessViolation
exception message : Access violation at address 00A1EEFF in module 'cMUD.exe'. Read of address 00000029.
Main ($5c98):
00a1eeff +57b cMUD.exe term 8529 +77 TTerm.PutText
00a1f605 +049 cMUD.exe term 8662 +2 TTerm.Add
00c932b9 +0b1 cMUD.exe MAIN 1571 +8 TMUDForm.OutputStr
00c935ac +0f4 cMUD.exe MAIN 1647 +22 TMUDForm.NextMUDLine
00c93a21 +019 cMUD.exe MAIN 1721 +4 TMUDForm.DoNextLine
00cdc46d +039 cMUD.exe MAIN 20880 +3 TMUDForm.ProcessMUDNow
00cd3f78 +0a0 cMUD.exe MAIN 18527 +12 TMUDForm.ExecCommand
00c5559b +0d7 cMUD.exe CodeThread 1184 +9 TRunCodeThread.DoExecCommand
0047dda1 +101 cMUD.exe Classes 9339 +22 CheckSynchronize
00c5450a +096 cMUD.exe CodeThread 468 +15 MsgWaitForSingleObject
00c54635 +029 cMUD.exe CodeThread 544 +4 WaitForThread
00ca3915 +1ed cMUD.exe MAIN 6150 +32 TMUDForm.ExecThread
00caa091 +4b9 cMUD.exe MAIN 8393 +94 TMUDForm.ExecTrig
00c6e929 +13d cMUD.exe PARENT 11797 +20 ExecAlarm
00c6ec2b +267 cMUD.exe PARENT 11859 +49 TrigTimer
77d4bcc7 +00a USER32.dll DispatchMessageA
0052f324 +0ac cMUD.exe Forms 6873 +13 TApplication.ProcessMessage
0052f36b +00f cMUD.exe Forms 6892 +1 TApplication.HandleMessage
0052f606 +0a6 cMUD.exe Forms 6976 +16 TApplication.Run
00dcbc28 +088 cMUD.exe CMUD 344 +18 initialization
7c91312f +069 ntdll.dll RtlUnicodeStringToAnsiString
7c812907 +0b6 kernel32.dll GetVersionExA |
|
|
_________________
The only good questions are the ones we have never answered before.
Search the Forums |
 |
|
|
Vijilante
SubAdmin
Joined: 18 Nov 2001
Posts: 5187
|
Posted: Sat Dec 01, 2007 7:48 pm
|
I have been looking into this more and I think this crash is actually the same bug that is demonstrated in my 500 thread test. It just happens at a different spot because of where the #SHOW is. Hopefully that is actually the case because I am having no luck at getting this exact crash point to replicate.
|
|
_________________
The only good questions are the ones we have never answered before.
Search the Forums |
|
|
|
|
|
|
