Re: [Bug-apl] script "Killed"

[Juergen Sauermann]

Hi,

if the problem was triggered by a lack of memory, then you can set
⎕SYL[3] to a reasonable nonzero value. That will stop the APL program when
the limit is reached, but remain in the interpreter.

I am unfortunately not aware of a method that can predict in a reliable, efficient,
and portable way, whether a memory allocation will succeed or not (or, for that
matter, if the system will start swapping).

/// Jürgen

On 02/17/2016 02:21 AM, Christian Robert wrote:

I would say that you are out of memory.

Killed alone means killed by the system.

# dmesg | tail -n 50

will probably confirm the out of memory condition.

Xtian.

On 2016-02-16 19:25, address@hidden wrote:

Hi Bug-APL,

I was running APL as a script, working on a file that is several megabytes, and it printed the word "Killed" and then ends and kicks me back out to the command line. Does anyone have any idea what happened here? Is this possible to avoid?

-Alex