Zugg Software :: View topic

Posted: Tue Jun 15, 2010 2:03 am

The following trigger seems to hang my system, but only at certain times:

Posted: Tue Jun 15, 2010 4:55 pm

I wasn't able to get any hang here. If you can get it to hang on certain text from your MUD, try creating a debug log file to send to me. Connect to your MUD, then type:

#DEBUGFILE test.raw test.txt

and then do whatever on the MUD to display the text that is causing the trigger to hang. Then exit CMUD and send me the test.raw and test.txt files as email attachments so I can try to replay them here.

Be sure to reference this forum post in your email so I can connect the two and use your above trigger and database variable.

Also, in your above debugger output, it shows your trigger firing on two lines:

Posted: Tue Jun 15, 2010 11:44 pm

yes i do, its a smaller stringlist of craftsets, but its not the one causing the issue as when i turn off the one i posted, things run smoothly {Apothecary|Apothecary-extractions|etc}.
I think the error is coming from the red colored text... i will send the .raw shortly,

Posted: Wed Jun 16, 2010 12:32 am

Is it possible that you have an infinite loop of triggers causing each other to fire? This would explain how turning off one of them fixes the issue.

You might want to create a new session with just the single trigger above and then test it on your MUD to see if it fails with just that trigger alone. That's what I'll be testing here with your raw file.

Posted: Wed Jun 16, 2010 2:23 am

Possible i suppose, but it still crashes when the other one is disabled, but here is the other one anyway

Posted: Wed Jun 16, 2010 4:14 pm

I didn't receive any files yet. Be sure you sent them to the sales@zuggsoft.com account.

If it bypasses the normal crash dump dialog, then it's some sort of infinite loop that is blowing away the memory stack.

Are you able to reproduce the crash in a fresh session with just the first trigger shown in the original post?

Posted: Wed Jun 16, 2010 4:52 pm

That was the problem. I had mailed it to support, not sales... I forwarded it just now.

Posted: Fri Jun 18, 2010 5:24 pm

Just wanted to follow up with this. I received the files and I was able to reproduce the hang. So hopefully I can fix it for the next release.

Posted: Fri Jun 18, 2010 5:31 pm

I'm glad it wasn't just me or corrupted settings for a change.

Posted: Fri Jun 18, 2010 8:23 pm

Not sure why this crashes now but not in previous versions. The issue was a problem with #SUB and is something I haven't messed with in a while.

I think I have this fixed in the next update, but I'd be interested in knowing if it also failed in 3.17 or earlier versions.

Posted: Sat Jun 19, 2010 3:51 am

It was in 3.17 when i reported the issue, seems fixed in 3.20

Posted: Sun Sep 12, 2010 4:01 pm

For some reason, this package is once again causing CMUD to hang in 3.25.

Apprentice Joined: 10 Apr 2009 Posts: 145

A bit off-topic, but I'm curious. What is your script and that huge list doing?

Posted: Mon Sep 13, 2010 3:56 pm

It turns crafts, the means of performing skilled labor on the mud in question, into a quick click link to see the procedure of, or to perform.

Posted: Mon Sep 13, 2010 4:49 pm

I have new data.
This is no longer an issue of the red colored text, that is indeed fixed.

But it is the same trigger and variable.

I have since found that the dbVar is getting corrupted some how to include some of the send data by the #SUB.

The command i used was 'say brawling'

Normally it prints like this:

Posted: Tue Oct 05, 2010 7:09 pm

A fix! (Thanks darmir)
But I don't understand why this fixes it......

change the trigger above from:

Posted: Tue Oct 05, 2010 7:53 pm

Further testing shows that the #NOOP #IF and %ismember have nothing to do with the error, i put them back in and so long as the #EXEC is there, nothing fails or corrupts.

I forget why I wanted them there originally... just getting rid of possible factors now.

i suspect its something in the <send> code.

Sorcerer Joined: 10 Oct 2000 Posts: 706 Location: USA

There is still the issue with the Perform menu not working correctly. If you try it the doesn't work. See the other thread I started about this.

Wizard Joined: 22 Mar 2007 Posts: 2320

Shalimar, the reason the #EXEC fixes it is because that part of the <SEND> has to be a command. Commands cannot start with a function or variable. They must start with an alias (explicitly written out--not an indirection through a variable), or a Cmud command (i.e. starting with #), or a mud command (again, explicitly written out). Even the mere mud command is better done with a #SEND command.

Posted: Wed Oct 06, 2010 12:58 pm

It USED to work a few beta versions ago... so this must not have always been the case. I had to change the script to make it compatible with the current version.

Wizard Joined: 22 Mar 2007 Posts: 2320

It has been the case from the beginning in Cmud. Under _some_ circumstances you can get a commandline to work with a variable or function at the beginning of the command, but it is not correct syntax and may stop working at any time. Using a variable or function at the beginning of a command line is unsupported and deprecated--technically, I believe it was incorrect syntax in Zmud as well, but Zmud was much more forgiving of syntax variations.

Posted: Thu Oct 14, 2010 5:26 pm

I posted this in another thread. You need to put a ~ character before the | character in the SEND command to prevent CMUD from parsing it as a string list for #SUB.

Posted: Fri Nov 12, 2010 8:59 pm

Posted: Fri Nov 12, 2010 9:34 pm

Yes, that was actually fixed in v3.31.