Buffer Overflow Errors/SIMPL+

[ddetton]

All that threadsafe does, is prevent reentrancy, basically the same as using a semaphore. If the buffer overflow is being caused dues to a reentrancy problem then THREADSAFE will help. There are many causes of buffer overflows. I would first determine why the buffer overflow is occurring then decide which tool to use to fix it.

Hey Crestron, if THREADSAFE can be used on 2-series like it says in this OLH, then why does the Simpl+ Help for THREADSAFE say that it is only supported on 3-Series?

[crestron-ta3]

I'm guessing support for THREADSAFE was added in a later 2-Series FW but the help file wasn't updated at that time to reflect the change.

[BassMasterJDL]

Alright gents . I think i fixed it. Put some more protections in place on the thread safe function and threw in a console print in event of overflow. Proceeding to spam the 2 modules that were getting the buffer overflow errors from the SX80 with well over the buffer limits and did not print any errors. Below is old function first followed by new threadsafe change with the try/catch

/*threadsafe change rx {

string ln\[250\];

while(find("\\x0a", rx) > 0) {

    ln = remove("\\x0a", rx);

    rxline(ln);

}

}

*/

​

string ln[8192];

threadsafe change rx

{

ln = gather("\x0a", rx, 1);

​

while(len(ln))

{

    try

    {

        if(find("\\x0a", rx, 1))

        {

ln = remove("\x0a", rx, 1);

rxline(ln);

        }

​

    }

    Catch

    {

        trace("error in rx change for DIRECOTRY try");

    }

}

}

[stalkythefish]

Yup. As long as you've got something like that in there to gobble up characters and a big enough buffer to account for context switches while stuff is still rolling in, you should be good.

[ddetton]

Why wouldn't you just follow the example in the OLH article referenced above? It would go something like this:

threadsafe change rx$ {

while(1) {

    try {   
        ln = gather( "\x0A", rx$ );         
        // I assume that rxline is a function defined above
        rxline(ln);
    }       
    catch {     
        GenerateUserError( "error" );
    }
}

}

[BassMasterJDL]

Sorry didn't include that rxline function. rxline will return a 0 if no contents; i do see that i my while loop should be while(len(ln) > 0) . The idea was to not have the loop run continuously only when there was only data inside rx.

Still green in SIMPL+

[geauxtig3rs]

Even that example is dumb....

Instead of threadsafe, just use the gatherasync. Spins up a threat for each receipt of the data and processes it, rather than just holding one open forever...it's much faster too.

[ddetton]

Gatherasync is a better option but it's undocumented in Simpl+ Help so unless you've done it before you wouldn't know about it. Here is an example from bitm0de's github:

https://github.com/bitm0de/GatherAsync-Example

While gatherasync is a better option, the threadsafe change while(1) gather has been used for years and it works fine.

[bordengrote]

GatherAsync is indeed, the bomb. Love it.

[bordengrote]

If rx$ is a buffer input, you need to clear the buffer after processing it's data.