Vladimir Lipsky <[EMAIL PROTECTED]> wrote: > Well, currently, test 61 in t/pmc/pmc.t causes an abrupt stop of > the test session with the segfault box popping up.
> if (PObj_active_destroy_TEST(b)) > VTABLE_destroy(interpreter, (PMC *)b); > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > Parrot_really_destroy(int 0, void * 0x002f39f8) line 964 + 22 bytes > It would be a time-saver for me to fix the bug if you lay out > some thoughts on this. So feel free to push the reply button. The test doesn't look any special. To get a clue what's going on, you would have to set a breakpoint at the offending line and inspect the PMC (in gdb speak): b dod.c:525 r t/pmc/pmc_61.pasm p *(PMC *) b p *((PMC *) b)->vtable c ... There is more then one PMC having an active_destroy flags set, you have to repeat above steps until you get at the failing one. valgrind has no hint about a problem with this test. > 0x4C56 leo
