← Back to team overview

sikuli-driver team mailing list archive

Re: [Question #663653]: Sikulix Crash

 

Question #663653 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/663653

    Status: Open => Answered

RaiMan proposed the following answer:
Twice in 6 months looks like a system hick-up to whatever reason.

stackoverflow
https://stackoverflow.com/questions/40878851/abort-trap-6-error-in-c-mac-terminal
quote """
The error means you are writing to memory you don't own. Will likely happen if you try to copy a string longer than the one you specified for food ('pizza'). In this case it could be cos you are copying the string into memory location assigned to a string constant.
"""

In this very complex setup of issuing different "commands" in different
environments there might be a glitch somewhere in the used components.

Since it is annotated to the java command used in runsikulix it must be
some problem with the java startup, probably related to the special
-X... settings.

Though not knowing your complete setup, I guess, to do all this less complex might be using a main SikuliX script that uses run, runscript and Popen.subprocess to do the rest.
PowerManger the would only run the main via runsikulix.
Such a setup would give you more possibilities to control failure situations.

... but might not be worth, to get rid of something, that happens twice
in six months.

You might think of some wrapping, that tries to repeat the failing
command in that situation.

-- 
You received this question notification because your team Sikuli Drivers
is an answer contact for Sikuli.