 |
Thinjon100
Apprentice
Joined: 12 Jul 2004
Posts: 190
Location: Canada
|
 Posted: Fri Sep 28, 2007 10:56 pm
[2.04] #STOP and crashes
|
For some reason, the last trigger that executes in one of my capture windows always shows up in #THREAD with a status of "stopped", even though the trigger is completely done executing (all it does is color a line and call an alias).
While trying to debug another weird behavior in 2.04, I did #STOP with the argument for the above-mentioned thread. A subsequent #THREAD shows it has been stopped, but the next trigger that fires crashes CMud. I've submitted a crash report on this, but I'm not sure if my description in the report detailed this sequence. |
|
_________________
If you're ever around Aardwolf, I'm that invisible guy you can never see. Wizi ftw! :) |
 |
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Fri Sep 28, 2007 11:27 pm
|
Could you show the exact trigger that is running? That might help give me more info. Also, is the trigger defined in the main window, or defined in the capture window?
|
|
|
|
|
Thinjon100
Apprentice
Joined: 12 Jul 2004
Posts: 190
Location: Canada
|
Posted: Fri Sep 28, 2007 11:51 pm
|
The trigger that is showing is in the capture window. The #THREAD report normally shows 1 of 5 triggers in that capture window, whichever executed last. Here's an example of one of them:
| Code: |
Regex pattern:
^--> ([a-zA-Z]{3,12})@([^\s]+) \(.*\) has connected\.$
Execution code:
#COL $339966
multiplay_logon %2 %1
|
multiplay_logon is an alias to execute some code in a class. Even though that class is currently disabled, these triggers are still showing in #THREAD.
And in case anyone is curious, this is part of a script I wrote to capture and check players connecting to my mud for multiplaying and alt-switching... so DON'T CHEAT! :P |
|
_________________
If you're ever around Aardwolf, I'm that invisible guy you can never see. Wizi ftw! :) |
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Sat Sep 29, 2007 1:23 am
|
Does it have any effect if you remove the alias from the trigger? I really need to see the *entire* execution chain (which includes the alias) to see why it isn't finishing the script properly.
|
|
|
|
|
Thinjon100
Apprentice
Joined: 12 Jul 2004
Posts: 190
Location: Canada
|
Posted: Sat Sep 29, 2007 1:59 am
|
I removed the alias... and after looking again, see that other triggers in that window (which have ONLY a single #color command) are sticking too... it appears it's whatever executed last in that window
|
|
_________________
If you're ever around Aardwolf, I'm that invisible guy you can never see. Wizi ftw! :) |
|
|
|
|
|
|
