Zugg Software :: View topic

Magician Joined: 18 Dec 2006 Posts: 317 Location: Denmark

I sometimes get an exception from CMUD probably because a variable is duplicated. Well, that is my best guess anyway as I often see this when I get an exception. Problem is that I don't know exactly how the duplicate was created. The duplicates are always created at the root, I never try to create the variable but I often do a "variable = something" operation. However this is always done in a section and allways with the same name so there should be no problem.

I think there is something vulnerable in the code or I'd like to hear good advice about how to avoid the problem. Thanks.

Posted: Sun May 09, 2010 8:06 pm

if the variable was in a class that was disabled it would be unseen and a new var gets created

Magician Joined: 18 Dec 2006 Posts: 317 Location: Denmark

It isn't though.

I have a variable called commandQueue. This is used here:

Wizard Joined: 22 Mar 2007 Posts: 2320

You're absolutely certain that there is no other piece of code trying to set @commandQueue? It looks like you have it handled correctly. Are all of the scripts that refer to @commandQueue in the same package? Is @commandQueue defined in the same package or a different one? Is the duplicate variable appearing in the same package as the scripts?

It looks like you have done the right things (assuming the answers I expect to the above questions). If you do have it set up correctly, it should be working fine. There have been reports of spurious duplicated variables before, but most cases were tracked down to one of: the variable or its class being disabled; a script defined in a package or window where it could not see the correct variable; or a script they forgot about creating the duplicate variable. A few cases have not been fully explained, perhaps due to insufficient information. No one has been able to show a repeatable procedure that created a duplicate variable when it shouldn't have. I suggest you a) double check all your code to see that every instance of @commandQueue is handled correctly, and b) try to find a repeatable procedure that creates the duplicate. Most likely that will simply identify a problem in your code, but it is always possible that there is a bug in Cmud. If so, a repeatable procedure is necessary before it can be fixed.

Posted: Mon May 10, 2010 2:55 am

I'm almost convinced it might be a threading issue. Why do I suppose that? Because recently I added a #WAIT to force a threading of my email script. Ever since that day, I've had two variables duplicate itself to the root folder. Never realized it until just now, though.

Charneus

Magician Joined: 18 Dec 2006 Posts: 317 Location: Denmark

Posted: Mon May 10, 2010 5:54 pm

In the above places where you show that you use the variable, where are these getting used? Are these in triggers, or aliases, or events, or functions, or what? If they are in triggers, then what class folder are the triggers in? Same folder as the variables? Or a different folder?

We need to see more details on your class structure layout and where this variable is being called to help with this.

Magician Joined: 18 Dec 2006 Posts: 317 Location: Denmark

The first two pieces are from an alias in the same folder as the variable. The third is from a function in the same folder and the fourth and last piece of code is from an alias in another folder.

I can send in the full code if it's of any use.

Wizard Joined: 22 Mar 2007 Posts: 2320

Is the folder containing the fourth piece of code in a different module or window from the others?

Magician Joined: 18 Dec 2006 Posts: 317 Location: Denmark

Same window.