Vladimir Lipsky <[EMAIL PROTECTED]> wrote: > Some time ago I mentioned I'd been gettin' one more segfault while the > Parrot debug mode was on. In fact, it proved to be an effect of the > same cause -- we have global resources sharable among interpreters, > that we try to free more than once. This time it's encoding_array. If > you're going to disable the encoding_array freeing for now, just make > sure you disable the chartype_array one either.
Did you recheck that after my fix to vtable freeing? My patch covered encoding and chartype too. > 0x4C56 leo
