It appears that SLQSStart() is changing the state of signal SIGCHLD to SIG_IGN, which affects the calling process. Any subsequent system calls that rely on wait(), waitpid(), system() etc… fail with an ECHILD (no child process) error.
Whilst it is common to set SIG_CHLD to SIG_IGN when ‘daemonizing’ an application, this is usually done AFTER a fork(), and hence the signal change only affects the ‘new’ child process.
Why is SLQSStart() changing a signal that affects the calling process? Is this a known bug?
[SLQS04.00.18 pre-compiled ARM binary] [I don’t have access to the SDK source code]