Re: [perl #122199] perl5.18 segfault after wait() when system don't have much free memory

On Sat, Oct 18, 2014 at 03:39:17AM +1100, L.O.Sim wrote:
> In the past, my application will run for 4 or more hours before core dumps> or funny perl internal errors start to happen. Then I managed to reduce it> to a small script that high-lights the problem.

Can you (or someone else with the ability to reproduce this) please run
this on a perl (the newest version you have access to), built with
debugging symbols (and preferably -DDEBUGGING), then provide a C-level
backtrace? Also, provide the 'perl -V' output for the perl you use.

Also if possible, run it under valgrind, or clang with Address Sanitizer,
and show what errors it reports.

-- 
Hofstadter's Law: It always takes longer than you expect, even when you
take into account Hofstadter's Law.