Apparently I have a 267 megabyte past_node_5.out file... And if
past_op_2.pir and past_val_2.pir were printed to a file, I imagine it'd
do the same(printing a lot of spaces). Seems to be more than just
Parrot::Test for me.
On Feb 4, 2006, at 12:54 PM, Allison Randal wrote:
On Feb 3, 2006, at 17:33, Joshua Isom via RT wrote:
But, I've encountered two major problems. On darwin, I can't finish
past_node.t, first parrot takes over 100 megs of ram, then perl(5.8.7)
wants 180 megs. On freebsd, it's actually worse, but more confusing.
It fails with past_*.t and post_*.t. But past.t is fine. It's
essentially a lot of out of memory errors(yet swap space isn't
touched,
and there's free ram at that moment). Darwin essentially starts
"stalling" when freebsd just gives up on allocating more memory. Line
numbers aren't given in the print out, except for src/memory.c line
92.
This is a known bug. As far as we can tell so far, it's not the Punie
code, but Parrot::Test causing the problem. On both platforms, try
running the generated .pir files in languages/punie/t directly (e.g.
t/past_node_2.pir). Everyone who's tried it so far has reported that
they have no memory errors running the test code directly, and only
get errors running the code through the test harness.
Allison
