Zugg Software :: View topic - Access violation at address 00D7B450 in module 'cMUD.exe'. Read of adress 000000

Beginner Joined: 19 Nov 2008 Posts: 14

Sorry if the subject line isn't letter perfect, but I tried to get close. I'm getting a lot of these memory access errors, but this is the first one that exhibits every time. Some others I was able to get past by deleting the existing trigger and re-creating. Some others by killing cMUD and restarting. Others by rebooting.

I'm getting a lot of these errors. Apart from this one, on the order of one every hour or two of uptime for cMUD. I'm running Vista Home Premium 64 with 8gb of ram. No other applications exhibit errors. This error (and others) exhibit whether or not cMUD is run as Administrator.

If there are config issues I need to take into consideration on Vista, or there is some fatal flaw in my approach in the trigger below, I would appreciate feedback. (Yes, I have submitted some error logs, and am willing to submit more via cMUD, but as that contains detailed personal info, I won't be posting those here.

<trigger name="trConSpells" priority="3020" language="Lua" id="302">
<pattern>Contains the spells: (*)</pattern>
<value>zs.var.gCurrSp = zs.param(1)
zs.gettrigger("trConSpells").enabled = false</value>
</trigger>

Posted: Sat Nov 29, 2008 9:03 am

Is CMUD's crash dump handler catching these errors? If so, seeing the dumps (you can save them to text files if the automatic uploading is failing for whatever reason) will help.

Beginner Joined: 19 Nov 2008 Posts: 14

This is the output I get in the log.

Posted: Sun Nov 30, 2008 12:08 am

Beginner Joined: 19 Nov 2008 Posts: 14

If this is a known issue, shouldn't that be posted somewhere?

This is a long weekend and Zugg deserves it as much as any, but I hope this isn't relegated to the "doesn't work with vista/vista 64" pile.

Posted: Mon Dec 01, 2008 6:01 pm

Actually, I am not aware of any x64 issues in CMUD right now. The only issues related to x64 used to be that DEP is enabled for all applications by default (see the CMUD Troubleshooting article). Also, earlier releases of x64 Windows had more problems, but I think Microsoft has fixed most of them. I know there are several people on these forums using x64 just fine.

The error in your crash dump looks like a problem with the Lua script. But I just tried it on my system here and it worked fine:

1) Run CMUD, close the Sessions window. Open the Settings Editor (Ctrl-G)
2) Copy your XML code from your post above, then right-click on the Tree view on the left side of the editor and select Paste.
3) On the command line, I typed:

#SHOW "Contains the spells: heal"

and it properly created the @gCurrSp variable with the value of "heal" and properly disabled the trigger.

So try this in a blank session to see if it works on your computer or not. My guess is there is some other complexity in your scripts causing it to fail in your specific character session.

But unless there is a problem with Lua itself on x64, I doubt that is the problem.

Edited: Although you should generally have a good reason to use LUA over the default zScript. It's faster to just use: