At 7:23 PM +0100 3/7/04, Leopold Toetsch wrote:
Dan Sugalski <[EMAIL PROTECTED]> wrote:
- It's been happening for quite a while.
This one is fixed already. I've here two more fixed - one (the final) is
still sitting around.
Yeah, I saw that. I do apologize for the recent flood of e-mail--what
I
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> - It's been happening for quite a while.
This one is fixed already. I've here two more fixed - one (the final) is
still sitting around.
leo
At 4:03 PM +0100 3/5/04, Leopold Toetsch wrote:
Jens Rieks <[EMAIL PROTECTED]> wrote:
Hi,
The following code crashes parrot if run with -t (trace).
Some more notes:
- it happens with or w/o ARENA_DOD_FLAGS
- it happens with the copying GC or with --gc=libc
- it does not happen with DOD/GC disab
Jens Rieks <[EMAIL PROTECTED]> wrote:
> The following code crashes parrot if run with -t (trace).
Fixed.
That was not an easy one. A slightly wrong implementation (braino
courtesy of leo) did reset interpreter->lo_var_ptr (the stack limit),
when reentering the run loop, e.g. in object's __init c
Jens Rieks <[EMAIL PROTECTED]> wrote:
> Hi,
> The following code crashes parrot if run with -t (trace).
Some more notes:
- it happens with or w/o ARENA_DOD_FLAGS
- it happens with the copying GC or with --gc=libc
- it does not happen with DOD/GC disabled
- I did not find any breakage in e.g. ex
Jens Rieks <[EMAIL PROTECTED]> wrote:
> Hi,
> The following code crashes parrot if run with -t (trace).
> It seems to be due to an unused .param, see line marked with XXX.
The unused param doesn't harm. The problem is memory corruption very
likely due to the PIO_printf code inside trace.c (or st
# New Ticket Created by Jens Rieks
# Please include the string: [perl #27391]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=27391 >
Hi,
The following code crashes parrot if run with -t (trace).
It seems to be due to an
