Perl-Sensitive Sunglasses | |
PerlMonks |
Re^3: How use $^M?by Fletch (Bishop) |
on Apr 05, 2021 at 14:40 UTC ( [id://11130845]=note: print w/replies, xml ) | Need Help?? |
There's a bit more of an explanation in perldiag for "Out of memory during request for %s" and I think this is presuming that you've compiled using perl's malloc. Out of memory during request for %s (X)(F) The malloc() function returned 0, indicating there was insufficient remaining memory (or virtual memory) to satisfy the request. The request was judged to be small, so the possibility to trap it depends on the way perl was compiled. By default it is not trappable. However, if compiled for this, Perl may use the contents of $^M as an emergency pool after die()ing with this message. In this case the error is trappable *once*, and the error message will include the line and file where the failed request happened. So iff you've got a perl with perl's malloc and you give a buffer to $^M and then run out of memory perl will die and write its error message to that buffer. In that case yes then you could trap that one exception, and you could see where the exception occurred (as opposed to just getting an "Out of memory" error from the OS' malloc maybe). As far as testing I *think* you could use something like ulimit -m to artificially lower how much memory's available to child processes. Allocate a small buffer as shown in the example, then try and create a large string (run ulimit -m 512 then try perl -E '$^M=(q{}x(1<<16));eval { $x = (q{FOO} x (512 * 1024 * 1024)); }; if($@){die $@;}')
The cake is a lie.
In Section
Seekers of Perl Wisdom
|
|