hello,
I am trying to read out strings from a file, check if they are a valid keywords and if so call a function or set a variable etc.. In most the cases the functions get called as expected, but sometimes the engine crashes in the function, which compares the strings.

After some debugging i found out, that the engine crashes at the str_cmpii function. So I checked if the strings are valid by outputting them with diag(). Both strings were correct, but the engine still crashed at that function.

As far as I could observe it, the crash isn't caused by a special string, but if the file size exceeds a limit.

So my question is what factors can cause this crash else, if both passed strings are 'valid'?

I think a had the same problem a while ago and it was fixed in an updated
version of GS. If that's not the problem then maybe try adding a bool to it
eg: if(str_cmpi(string1,string2) == 0)

From the manual
These functions return TRUE if the strings are equal. This is different to C / C++ where similar functions return FALSE when the strings are equal.

Good luck.

A user - maybe it was you? - already reported a crash of str_cmpi some time ago and we thoroughly checked that function on that occasion. So I'm pretty sure that str_cmpi is flawless. However it may have something to do with the rest of your project.

For instance, when internal memory is overwritten over the end of a STRING struct, then functions like str_cmpi can indeed crash. Overwriting internal memory can happen, for instance, by loading a file with faulty content.

We had also problems with some other str_* functions in one of our bigger projects. We've increased the nexus and everything works fine...

I am pretty sure there are no files with faulty content, but I'll check the malloc/free calls and my array indexing etc again...

Zapan: When string functions crash depending on random conditions, such as the size of the nexus, then internal memory is most likely overwritten. It can be a bug in the script, or a damaged file with wrong internal pointers. This project will behave unstable.

Generally, if something bad happens in a project, increasing the memory in the hope that it will then crash less often is the wrong strategy. Better try the opposite, establish some worst case condition where is always crashes. This way you'll find the reason more easily by temporarily eliminating parts of your code.

The Problem is solved.
Scorpion bekommt jetzt 3 Tage keine Schokolade.

Der Fehler ist zu peinlich um Ihn zu beschreiben.

-.- bist du wieder nett
Es lag an einem array, dem falsche werte zugewiesen wurden.