Zugg Software :: View topic

Posted: Sun Mar 27, 2005 9:07 pm

I've been getting a few access violations in "Zmud.exe". These usually occur when I'm receiving a lot of text from the mud or sending a few commands at once.

I've also been getting parsing errors in the same situation. They've listed a few different triggers and I'll mention the parts I remember here. The bold parts are what showed up in the box.

#TRIGGER {&{hp}h, &{mn}m, &{ed}e, &{wp}w ([cexkdb@])~-} {
VAR/prompt=%5
#IF (%pos( x, %5)) {VAR/balance=1} {VAR/balance=0}
#IF (%pos( e, %5)) {VAR/equil=1} {VAR/equil=0}
#IF (%pos( k, %5)) {
ondef kola
unafflict unkola
} {
undef kola
afflict unkola
}
#IF (%pos( c, %5)) {ondef cloak} {undef cloak}
#IF (%pos( d, %5)) {
ondef deaf
unafflict undeaf
} {
undef deaf
afflict undeaf
}
#IF (%pos( b, %5)) {
ondef blind
unafflict unblind
} {
undef blind
afflict unblind
}
VAR/ignoring=0
} "" {nocr|prompt}
#ALIAS sp {#forall @VAR/pipecures {#if (%ismember( %{i.1}, @VAR/afflictions)) {%{i.2}}}}
and finally
#VAR VAR/hypnoq %delnItem( @VAR/hypnoq, 1)

Is there anyway to fix this, or is it just the result of too much spam and poor coding?

SubAdmin Joined: 18 Nov 2001 Posts: 5182

The access violations could be caused by something entirely different that is damaging the memory and showing up in these places. However if the first reports of it consistently point to this trigger and alias then they are likely at fault.

One thing I noted in you alias:
#ALIAS sp {#forall @VAR/pipecures {#if (%ismember( %{i.1}, @VAR/afflictions)) {%{i.2}}}}
Without knowing the contents of your pipecures variable looks like it should be
#ALIAS sp {#forall @VAR/pipecures {#if (%ismember( @{%{i}.1}, @VAR/afflictions)) {@{%{i}.2}}}}

Posted: Mon Mar 28, 2005 2:46 am

Sorry I didn't include the variable in the first post. The SP alias works fine as is, but I occasionally get that parsing error. The variable looks something like this.

#VAR pipecures {(affliction|cure)|(affliction|cure)|(affliction|cure)}

Posted: Mon Mar 28, 2005 4:42 am

Okay, I had the parsing error and access violation show up again.

The parsing error seems universal, every time I change a variable or run something it gets angry at me.

A window shows up saying:
Parse Error
Error parsing command:
Invalid Pointer Operation
#VAR VAR/variable %delItem( "item", @VAR/variable)

Other parse errors are as simple as variable=2

This is happening whenever any trigger fires, but it appears to start when the following Alarm goes off:

SubAdmin Joined: 18 Nov 2001 Posts: 5182

I can't really see anything in there that would initially cause the problem. As I said in my first reply once the parsing system gets horked by an invalid pointer it often affects other syntax. While zMud is very good at detecting such error and stopping them the script language is very complex and often has multiple methods for achieving the same end. This means that you may not even get the error detected on the script causing it, but may have it appear on every subsequent thing. You may have to post/email a complete export your scripts for others to examine for odd syntaxes.

Posted: Mon Mar 28, 2005 9:30 pm

Posted: Tue Mar 29, 2005 1:28 am

Could I get an invalid pointer operation or access violatoin for attempting to do delete an item which is not a member of a string?
#VAR VAR/variable {var1|var2|var3|var4}
#VAR VAR/variable %delItem( "item1", @VAR/variable)

Or if I'm using
#IF (!@variable) instead of #IF (@variable=0) ?

Posted: Thu Mar 31, 2005 1:41 am

I'm still unable to solve this problem...

Could these errors be caused by:
#VAR variable {@var1|@var2|@var3} ?

And recently a new access violation popped up. Instead of the standard "Zmud.exe" its now in "ntdll.dll" (not sure why its there...)

Or could these be solved by reinstalling Zmud?