LPMuds.net

Lib Discussion => Dead Souls Support => Topic started by: balliol on October 02, 2008, 01:05:47 pm

Title: strange errors when creating something or casting spells
Post by: balliol on October 02, 2008, 01:05:47 pm
Hello,

I'm a newbie to the ds system, and have just installed it.
However, when i try to create something, i get the following error:
2008.10.02-19.50,53
*Array index out of bounds.
Object: /secure/sefun/sefun at /secure/sefun/strings.c:506
'<fake>' at /secure/save/creators/b/balliol (/<driver>) at line 0
'cmdAll' at /secure/save/creators/b/balliol (/lib/command.c) at line 162
'cmd' at /secure/cmds/builders/create at line 36
'gmake' at /secure/obj/staff#36 (/secure/modules/generic.c) at line 79
'last_string_element' at /secure/sefun/sefun at /secure/sefun/strings.c:506
Trace written to /log/runtime

I tried ds on a different computer, and there it also gave errors when i was trying to cast a spell, but that seems to work now.
The syntax i try for creating is create npc joe, and create vendor blah. I am aware the name after npc is the filename, but still this should work.
If someone would be able to help me with this, it'd be greatly appreciated.

Thanks,
Balliol
Title: Re: strange errors when creating something or casting spells
Post by: cratylus on October 02, 2008, 01:07:48 pm
Interesting.

Please try it with 2.9a9

Also, what is the exact command you issue to make this happen?

-Crat
Title: Re: strange errors when creating something or casting spells
Post by: cratylus on October 02, 2008, 01:51:52 pm
Quote
If someone would be able to help me with this, it'd be greatly appreciated.

I was able to reproduce this by doing the following:

* Installed Dead Souls 2.8.4 on Windows XP Pro.
* With my cwd as '/', tried to use the create command to make an NPC.

However, when I changed my working directory to something else,
the error did not occur. It appears there is a bug in strings.c in 2.8.4
triggered by using QCS with '/' as the working directory. I have not
tried it on other OSes, but I imagine this will also happen on UNIX.

The workaround is to be in some other directory while using QCS.

This is fixed in 2.9a9. I was not able to reproduce the error on that version.

-Crat