On Sun Sep 07 15:19:22 2008, cotto wrote:
On Thu Jun 12 10:23:06 2008, [EMAIL PROTECTED] wrote:
On Thursday 12 June 2008 10:01:21 NotFound wrote:
Some more details: adding:
Parrot_set_flag(interp, PARROT_DESTROY_FLAG);
in src/main.c it segfaults also when executing with
On Thu Jun 12 10:23:06 2008, [EMAIL PROTECTED] wrote:
On Thursday 12 June 2008 10:01:21 NotFound wrote:
Some more details: adding:
Parrot_set_flag(interp, PARROT_DESTROY_FLAG);
in src/main.c it segfaults also when executing with perl6.pbc, and
also a lot of parrot test fails.
So
Some more details: adding:
Parrot_set_flag(interp, PARROT_DESTROY_FLAG);
in src/main.c it segfaults also when executing with perl6.pbc, and
also a lot of parrot test fails.
So it looks like there is a general problem of interpreter destruction
in exits from the exception handler.
--
Salu2
On Thursday 12 June 2008 10:01:21 NotFound wrote:
Some more details: adding:
Parrot_set_flag(interp, PARROT_DESTROY_FLAG);
in src/main.c it segfaults also when executing with perl6.pbc, and
also a lot of parrot test fails.
So it looks like there is a general problem of interpreter
# New Ticket Created by Seneca Cunningham
# Please include the string: [perl #55372]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=55372
I had started an attempt to determine which test in rakudo's spectest
was
On Fri, Jun 6, 2008 at 4:39 AM, via RT Seneca Cunningham
[EMAIL PROTECTED] wrote:
I had started an attempt to determine which test in rakudo's spectest
was causing a SIGBUS on my system (OS X 10.5, ppc) by manually running
tests that occurred at the appropriate moment in time when the first
