segfault in ?? (directory_destroy)

[coke]

When running ./tclsh and immediately exiting by hitting ^{D; we get a segfault.}

parrot: r41161; partcl r701

bt:

#0  0x080b52d8 in ?? ()
#1  0xb7e181b8 in directory_destroy (interp=0x8051008, self=0x8106808)
    at src/packfile.c:2205
#2  0xb7e180d2 in PackFile_Segment_destroy (interp=0x8051008, self=0x8106808)
    at src/packfile.c:1800
#3  0xb7e181b8 in directory_destroy (interp=0x8051008, self=0x80eedf8)
    at src/packfile.c:2205
#4  0xb7e180d2 in PackFile_Segment_destroy (interp=0x8051008, self=0x80eedf8)
    at src/packfile.c:1800
#5  0xb7e1c368 in PackFile_destroy (interp=0x8051008, pf=0x80eedf8)
    at src/packfile.c:545
#6  0xb7e078d3 in Parrot_really_destroy (interp=0x8051008, exit_code_unused=0, 
    arg_unused=0x0) at src/interp/inter_create.c:418
#7  0xb7df5d91 in Parrot_exit (interp=0x8051008, status=0) at src/exit.c:91
#8  0xb7df577e in die_from_exception (interp=0x8051008, exception=0xb6d41a00)
    at src/exceptions.c:169
#9  0xb7df5be7 in Parrot_ex_throw_from_op (interp=0x8051008, 
    exception=0xb6d41a00, dest=0x80ef6e0) at src/exceptions.c:239
#10 0xb7dcac93 in Parrot_exit_ic (cur_opcode=0x80ef6d8, interp=0x8051008)
    at src/ops/core.ops:893
#11 0xb7e2297b in runops_slow_core (interp=0x8051008, runcore=0x80dfe38, 
    pc=0x80ef6d8) at src/runcore/cores.c:955
#12 0xb7e2147e in runops_int (interp=0x8051008, offset=522)

[NotFound]

This was fixed some weeks ago, isn't it?

[coke]

On Fri, Sep 25, 2009 at 5:36 PM, Parrot <parrot-tickets@lists.parrot.org> wrote:
> Comment(by NotFound):
>
>  This was fixed some weeks ago, isn't it?

Yes, this can be closed.



-- 
Will "Coke" Coleda