I'd say you need to track the growth of your memory consumption. Not sure what the codepoint can tell you.
You probably have a memory leak due to recursive data structures.
update
according to splain -v it's non-trappable
DESCRIPTION OF DIAGNOSTICS
These messages are classified as follows (listed in increasing ord
+er of
desperation):
(W) A warning (optional).
(D) A deprecation (enabled by default).
(S) A severe warning (enabled by default).
(F) A fatal error (trappable).
(P) An internal error you should never see (trappable).
=====> (X) A very fatal error (nontrappable).
(A) An alien error message (not generated by Perl).
...
Trappable errors may be trapped using the eval operator. See
"eval" in perlfunc. In almost all cases, warnings may be selectiv
+ely
disabled or promoted to fatal errors using the warnings pragma.
See warnings.
Out of memory! (#1)
(X) The malloc() function returned 0, indicating there was insuffi
+cient
remaining memory (or virtual memory) to satisfy the request. Perl
+ has
no option but to exit immediately.
At least in Unix you may be able to get past this by increasing yo
+ur
process datasize limits: in csh/tcsh use limit and
limit datasize n (where n is the number of kilobytes) to check
the current limits and change them, and in ksh/bash/zsh use ulimit
+ -a
and ulimit -d n, respectively.
Well ...
... probably the trace options of the debugger can help?
If you log them to a file, you should see where they stop.