Re: Debugging CPAN problem

If a program crashes, it's SIGSEGV that kills it. This results in a different message.

$ perl -e'kill SEGV => $$'
Segmentation fault
[download]

Killed is received from SIGKILL.

$ perl -e'kill KILL => $$'
Killed
[download]

I've gotten this when I used too many resources on a shared system (e.g. too much memory or CPU time). Check your ulimits and with your administrator. (I have limits even though ulimit doesn't list any.)

Update: oh, I see you did mention something along those lines. But...

Searching for an answer suggests that this is the OS killing CPAN and the most probable cause is lack of memory. The development unit has a 32Gb SD card

RAM, not disk space.

Comment on Re: Debugging CPAN problem Select or Download Code

Replies are listed 'Best First'.
Re^2: Debugging CPAN problem by ikegami (Patriarch) on Dec 22, 2020 at 22:28 UTC
If it is using too much CPU in a short time, you might have luck lowering the priority of the process. `nice cpan ...`.	[reply] [d/l]
Re^2: Debugging CPAN problem by Bod (Parson) on Dec 27, 2020 at 16:57 UTC
RAM, not disk space Both the production and the development machines have the same amount of RAM - 512Mb One installs fine from CPAN and the other one doesn't... It will probably always remain a bit of a mystery as I installed HTTP::Server::Simple using the information marto helpfully shared. The production unit is all boxed up ready to be connected to the curtains it will control once the immediate festive activity has passed. Regardless - knowing that Killed is received from SIGKILL was very helpful, thanks.	[reply]
Re^3: Debugging CPAN problem by ikegami (Patriarch) on Dec 28, 2020 at 18:31 UTC
How much RAM a machine has is not particularly relevant. Other factors can limit a process's memory. I specifically mentioned you should be looking into limits imposed by the system as these have been known to send SIGKILL to handle processes exceeding the limits. Re: Debugging CPAN problem provides a concrete example.	[reply]
Re^3: Debugging CPAN problem by stevieb (Canon) on Dec 27, 2020 at 17:51 UTC
You should have sent the unit before the festivities wrapped up... that way you could say that you were responsible for the automation of the "closing of the curtains" of this dumpster fire that has been the year 2020 :D	[reply]
Re^4: Debugging CPAN problem by Bod (Parson) on Dec 27, 2020 at 19:48 UTC
You should have sent the unit before* the festivities wrapped up...* I'm hoping it will be installed before 2021 arrives and that I'll be able to close the curtains on 2020 :) I have a connection onto the controller so I can make it happen remotely!	[reply]


XP is just a number
	PerlMonks