From: Tom Metro tmetro-boston...@vl.com
Date: Tue, 08 Mar 2011 02:31:34 -0500
. . .
I'm curious what their motivations are. Is a freely available CPAN
account useful for anything? Or is it merely an the first step in
gathering data for identity theft? Asking for date of birth
Small number so far. More ?
Bill, typing with thumbs
- Original Message -
From: boston-pm-announce-bounces+william.ricker=fmr@mail.pm.org
boston-pm-announce-bounces+william.ricker=fmr@mail.pm.org
To: Boston Perl Mongers (announce) boston-pm-annou...@pm.org; Boston PM
hi all,
we seem to have a low head count for tonight. maybe i can offer some
reasons to come by. i will be going over not only the new features in
File::Slurp but some interesting coding tricks in it and its tests. one
involves overriding core functions for testing. another involved
splitting
Some code I'm working on is triggering an out of memory error, and I'd
like to figure out what specifically is responsible. (It's a complex
system with dozens of libraries and it runs in parallel across a cluster
of machines. Running the code in a debugger isn't a practical option.)
Any
You can trap OOM if your Perl is compiled to use $^M, which your Perl
probably isn't. Otherwise... if I were you I'd look into a combination of
old-fashioned sprinkle print statements everywhere and maybe some deep
magic to attach them to the start of every sub.
That said, even if you do trap
From: Tom Metro tmetro-boston...@vl.com
Date: Tue, 08 Mar 2011 22:52:21 -0500
Some code I'm working on is triggering an out of memory error, and I'd
like to figure out what specifically is responsible. (It's a complex
system with dozens of libraries and it runs in parallel across a
I haven't tried this, but I have been mulling it for some time: using Dtrace to
debug Perl.
Of course, you'd have to be on *BSD or OS-X (or Soracle), But if that's Ok,
using runtime probes seems very promising for the memory leak/out of memory
problem area. I saw a good tutorial at OSCON on
TM == Tom Metro tmetro-boston...@vl.com writes:
TM Some code I'm working on is triggering an out of memory error, and I'd
TM like to figure out what specifically is responsible. (It's a complex
TM system with dozens of libraries and it runs in parallel across a cluster
TM of machines.
On Tue, Mar 8, 2011 at 7:52 PM, Tom Metro tmetro-boston...@vl.com wrote:
Some code I'm working on is triggering an out of memory error, and I'd
like to figure out what specifically is responsible. (It's a complex
system with dozens of libraries and it runs in parallel across a cluster
of
Conor Walsh wrote:
You can trap OOM if your Perl is compiled to use $^M...
http://perldoc.perl.org/perlvar.html
$^M
By default, running out of memory is an untrappable, fatal error.
However, if suitably built, Perl can use the contents of $^M as an
emergency memory pool after die()ing.
Federico Lucifredi wrote:
I haven't tried this, but I have been mulling it for some time: using
Dtrace to debug Perl.
...using runtime probes seems very promising for the memory
leak/out of memory problem area. I saw a good tutorial at OSCON on
the subject, and it had a Python section, I
Uri Guttman wrote:
if you run out of vram and you didn't expect it, wouldn't that signify a
possible leak?
No, not necessarily. This is code that processes large flat files,
supplementing them with information pulled from a few large lookup
tables which are loaded into memory, as well as
12 matches
Mail list logo
