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 calls. This lead to memory corruption if a DOD or GC was triggered inside the method call. During tracing, a lot of string handling is done, which sooner or later always exposed the bug. > jens leo
