LSL Errors

Script run-time error messages

A script may stop running, and chat at you the complaint "Script run-time error", followed by another complaint such as:

• Lists may not contain lists

• Math Error - float divided by zero, integer divided by zero, etc.

• Stack-Heap Collision - The Stack has collided with the Heap.
  The LSL memory space contains three sections Bytecode, Stack and Heap which all must be contained in 16kib of memory.
  • This can occur if the running script is too big. The script compiles and saves successfully, but when an object containing it is instantiated the script crashes.

Sample scripts that demo script run-time error messages

default
{
    state_entry()
    {
        list once = [];
        list twice = [once, once]; // Script run-time error: Lists may not contain lists
    }
}

default
{
    state_entry()
    {
        float one = 1.0;
        float zero = 0.0;
        float quotient = one / zero; // Script run-time error: Math Error
        llOwnerSay((string) quotient);
    }
}

Surprising compile-time ERROR messages

The SL GUI may reject some code that you feel is perfectly clear, printing ERROR at you and then explaining with some further complaint.

Examples follow ...

You must name the .x .y .z .s components of a vector or rotation that you're assigning, you can't assign them all at once from a list, for instance:

default
{
    state_entry()
    {
        vector vec = (vector) [1, 2, 3]; // Type mismatch
        llOwnerSay((string) vec);
    }
}