# New Ticket Created by Simon Glover
# Please include the string: [perl #22343]
# in the subject line of all future correspondence about this issue.
# <URL: http://rt.perl.org/rt2/Ticket/Display.html?id=22343 >
Currently, if you're in the debugger, and do anything that causes an
internal_exception call within the interpreter, you get a segfault.
Sample backtrace:
#0 0x080dfe9b in free_unused_pobjects (interpreter=0x81390c8,
pool=0x814e5f0)
at dod.c:345
#1 0x080df84c in Parrot_destroy_header_pools (interpreter=0x81390c8)
at headers.c:359
#2 0x0804a5bf in Parrot_really_destroy (exit_code=1, vinterp=0x81390c8)
at interpreter.c:622
#3 0x080e09e7 in Parrot_exit (status=1) at exit.c:66
#4 0x080e5232 in internal_exception (exitcode=1,
format=0x81063d4 "Array index out of bounds!\n") at exceptions.c:26
...etc
I think what's happening is that we're trying to destroy the interpreter
that pdb itself is using, which will clearly cause bad things to happen.
Simon
