Michael Norrish wrote:
On 13/05/10 11:01, Michael Norrish wrote:
The presence of Killed makes me think that the script is being killed
by an external signal, perhaps a SIGSEGV caused by hitting a limit on
stack-size. But is this plausible? Would Poly/ML catch that signal and
then exit with
I have a Linux shell-script that calls
poly-image script
and which is being dying unexpectedly in a cronjob. The end of the log looks
like:
Poly/ML 5.3 Release
Killed
/home/michaeln/stdhol/bin/Holmake: Failed script build for
arm_improved_gcScript - exited with code 89
Build failed in
On 13/05/10 11:01, Michael Norrish wrote:
The presence of Killed makes me think that the script is being killed
by an external signal, perhaps a SIGSEGV caused by hitting a limit on
stack-size. But is this plausible? Would Poly/ML catch that signal and
then exit with 89?
Experiments reveal
