 |
chamenas
Wizard
Joined: 26 Mar 2008
Posts: 1547
|
 Posted: Tue Jan 06, 2009 10:12 pm
Oninput Trigger made CMUD crash
|
| Code: |
<trigger name="Read" type="Command Input" priority="2380" regex="true" enabled="false" id="238">
<pattern>read ([\w'- ]+)page (\d+)</pattern>
<value>curr_book=%1
curr_page=%2</value>
</trigger>
|
Bug Report:
| Code: |
date/time : 2009-01-06, 17:06:08, 524ms
computer name : XXXXX
user name : XXXXX
registered owner : XXXXX
operating system : Windows XP Service Pack 2 build 2600
system language : English
system up time : 34 minutes 1 second
program up time : 20 minutes 37 seconds
processors : 2x Intel(R) Core(TM)2 Duo CPU T7100 @ 1.80GHz
physical memory : 2082/3063 MB (free/total)
free disk space : (C:) 18.80 GB
display mode : 1280x800, 32 bit
process id : $13ac
allocated memory : 34.07 MB
executable : cMUD.exe
exec. date/time : 2008-10-31 12:09
version : 2.37.0.0
compiled with : BCB 2006/07
madExcept version : 3.0h
contact name : XXXXX
contact email : XXXXX
callstack crc : $29698f51, $9d92226d, $9d92226d
exception number : 2
exception class : Exception
exception message : Error in trigger pattern: read ([\w'- ]+)page (\d+) range out of order in character class (145).
Main ($13a8):
00a19548 +518 cMUD.exe Search2 731 +87 FindPattern
00ccbcb9 +3a5 cMUD.exe MAIN 11467 +64 TMUDForm.InputTrigger
00cb5e0e +092 cMUD.exe MAIN 4179 +10 TMUDForm.RecordSendStr
00c6d936 +00e cMUD.exe CodeThread 1294 +0 TRunCodeThread.DoRecordSendStr
0047a54d +0fd cMUD.exe Classes CheckSynchronize
00c6c4b1 +0ed cMUD.exe CodeThread 508 +28 MsgWaitForSingleObject
00c6c5d4 +024 cMUD.exe CodeThread 580 +4 WaitForThread
00cbdc44 +244 cMUD.exe MAIN 6580 +52 TMUDForm.ExecComThread
00cbeb86 +46a cMUD.exe MAIN 6826 +47 TMUDForm.NewProcessStr
00cbd66d +009 cMUD.exe MAIN 6447 +2 TMUDForm.ProcessStr
00cbd107 +03b cMUD.exe MAIN 6322 +10 TMUDForm.ParseCommand
00ccf2c5 +23d cMUD.exe MAIN 12709 +34 TMUDForm.Command
00cd0626 +25e cMUD.exe MAIN 13062 +37 TMUDForm.FormKeyDown
00cfa1ab +013 cMUD.exe MAIN 22207 +1 TMUDForm.UserInKeyDown
004c0828 +020 cMUD.exe Controls TWinControl.KeyDown
0097a02b +013 cMUD.exe RVScroll 568 +1 TRVScroller.KeyDown
0091daa0 +014 cMUD.exe RichView 1970 +1 TCustomRichView.KeyDown
008ece9c +044 cMUD.exe RVEdit 1768 +6 TCustomRichViewEdit.KeyDown
004c08c4 +090 cMUD.exe Controls TWinControl.DoKeyDown
004c08e6 +00a cMUD.exe Controls TWinControl.WMKeyDown
008ecdbe +206 cMUD.exe RVEdit 1742 +41 TCustomRichViewEdit.WMKeyDown
004bac60 +024 cMUD.exe Controls TControl.Perform
004c1302 +0b2 cMUD.exe Controls TWinControl.CNKeyDown
004bafd3 +2bb cMUD.exe Controls TControl.WndProc
004befd7 +4fb cMUD.exe Controls TWinControl.WndProc
004be700 +02c cMUD.exe Controls TWinControl.MainWndProc
0047c3b0 +014 cMUD.exe Classes StdWndProc
7e4196c2 +00a USER32.dll DispatchMessageA
004a96ac +0fc cMUD.exe Forms TApplication.ProcessMessage
004a96e6 +00a cMUD.exe Forms TApplication.HandleMessage
004a99db +0b3 cMUD.exe Forms TApplication.Run
00df80e0 +088 cMUD.exe CMUD 348 +20 initialization
7c91312f +069 ntdll.dll RtlUnicodeStringToAnsiString
7c812b94 +0b6 kernel32.dll GetVersionExA
error details:
Inputting text to the MUD
|
All I did was input text that should have, in no way, fired the trigger. |
|
|
|
|
Vijilante
SubAdmin
Joined: 18 Nov 2001
Posts: 5182
|
Posted: Tue Jan 06, 2009 10:20 pm
|
You can safely continue from that error. What it is saying is that the trigger doesn't compile and passing along the error from the regex engine. Basically what happened is you entered the trigger, then entered some text. The text was causing CMud to check through #ONINPUT triggers and when it found one that wasn't compiled it tried compiling it. That failed so it was reporting that back through an exception instead of a pop-up. I am guessing Zugg forgot about that spot when he added reporting about pattern errors.
|
|
_________________
The only good questions are the ones we have never answered before.
Search the Forums |
 |
|
|
chamenas
Wizard
Joined: 26 Mar 2008
Posts: 1547
|
Posted: Tue Jan 06, 2009 10:42 pm
|
*nods* I have been continuing, it would just be annoying to get that whenever I entered text to the MUD. How do I get it to not try and compile when the pattern doesn't match any of the ONINPUT triggers?
|
|
|
|
|
Fang Xianfu
GURU
Joined: 26 Jan 2004
Posts: 5155
Location: United Kingdom
|
Posted: Tue Jan 06, 2009 10:50 pm
|
It's not that, it's because your pattern has an error in it (we already told you the fix for that in the other thread), and so the pattern doesn't compile. When it comes time to match, it tries to compile this uncompiled pattern, but encounters the same error. Fixing the error will make this go away.
|
|
|
|
|
chamenas
Wizard
Joined: 26 Mar 2008
Posts: 1547
|
Posted: Tue Jan 06, 2009 11:04 pm
|
I fixed the error though, the patterns work fine. The text I entered was unrelated to the pattern, it was something like "say blah blah blah".
Edit: Whoops, must not have saved or something. I thought I changed it, there, sorry about that. But doesn't it seem a little silly to error if your input in no way matches the oninput trigger? |
|
|
|
|
Fang Xianfu
GURU
Joined: 26 Jan 2004
Posts: 5155
Location: United Kingdom
|
Posted: Tue Jan 06, 2009 11:19 pm
|
No, because the pattern still has to be compiled so it can be tested. Until the pattern is compiled and tested, CMUD has no way of knowing whether it's similar or not. It's probably bad that this comes up with an AV rather than some other report, but there's definitely an error here that CMUD needs to tell you about.
|
|
|
|
|
|
|
|
