William Coleda <[EMAIL PROTECTED]> wrote:
> So, it's possible for someone to crash parrot by writing questionable PIR? ^_^
Yes. It's assembler programming basically. But eventually we'll have to
set GCed items in such a way that an access doesn't segfault but throws
an exception.
> (This was work
So, it's possible for someone to crash parrot by writing questionable PIR? ^_^
(This was working fine for quite some time, btw.)
Also, what do I need to do to save these subroutines? I'm doing dynamic
dispatch based on the tcl commands, so
proc foo {} {
puts "foo"
}
defines a sub in parrot's "Tcl"
William Coleda <[EMAIL PROTECTED]> wrote:
> Running the tcl "examples/bench.tcl" script, I get the following backtrace:
> Program received signal EXC_BAD_ACCESS, Could not access memory.
> 0x0021cb38 in Parrot_Sub_invoke (interpreter=0xd001a0, pmc=0xed2b60,
> next=0xf20284) at classes/sub.c:239
>
Running the tcl "examples/bench.tcl" script, I get the following backtrace:
Program received signal EXC_BAD_ACCESS, Could not access memory.
0x0021cb38 in Parrot_Sub_invoke (interpreter=0xd001a0, pmc=0xed2b60,
next=0xf20284) at classes/sub.c:239
239 if (interpreter->code->cur_cs != sub->se
